REST: From Research to Practice 2011
DOI: 10.1007/978-1-4419-8303-9_2
|View full text |Cite
|
Sign up to set email alerts
|

REST and Web Services: In Theory and in Practice

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
29
0

Year Published

2012
2012
2023
2023

Publication Types

Select...
5
4

Relationship

0
9

Authors

Journals

citations
Cited by 45 publications
(29 citation statements)
references
References 15 publications
0
29
0
Order By: Relevance
“…On the contrary, WS-* services exhibit all but the first property. A uniform interface shared by all services plus non-standardized documentation make the automatic discovery of RESTful services very hard in public repositories (Adamczyk et al, 2011). Besides, RESTful Web Services currently do not use a standardized format for representing resources -e.g., XML messages.…”
Section: Related Workmentioning
confidence: 99%
“…On the contrary, WS-* services exhibit all but the first property. A uniform interface shared by all services plus non-standardized documentation make the automatic discovery of RESTful services very hard in public repositories (Adamczyk et al, 2011). Besides, RESTful Web Services currently do not use a standardized format for representing resources -e.g., XML messages.…”
Section: Related Workmentioning
confidence: 99%
“…Due to the high demand of computational power, graph generation and optimisation are performed on the server side. Client-server communication is realised via a RESTful web service [36]. Figure 2 shows the routing criteria definition interface of the designed Add-In.…”
Section: Methodsmentioning
confidence: 99%
“…The advantage of including cache constraints is to improve the efficiency, scalability, and performance and reduce the latency of interactions. The methods used are GET, POST, PUT and DELETE operations [3] which are based on the http method used to create, retrieve, update, and delete operations on resources, respectively. The restful approach significantly reduces the transparencies that are caused by the required processing of SOAP-based messages due to the open and uniform identifying scheme.…”
Section: Rest Principlesmentioning
confidence: 99%
“…REST does not restrict client-server communication to a particular protocol, but it is the most commonly used with HTTP because HTTP is the primary transfer protocol. The building blocks of the Web are called resources [3].Resources are manipulated through messages that have standard meanings on the Web called as HTTP methods. Resources are named with uniform resource identifier (URIs) [2].…”
Section: Introductionmentioning
confidence: 99%