This link has been bookmarked by 491 people . It was first bookmarked on 02 Jul 2006, by craig hancock.
-
29 Mar 20
-
30 Aug 16
-
05 Apr 16
-
25 Aug 15
-
04 Jun 15
-
03 Jan 15
-
12 Nov 14
stuza1 .REST - An Architectural Style, Not a Standard
REST is not a standard. You will not see the W3C putting out a REST specification. You will not see IBM or Microsoft or Sun selling a REST developer's toolkit. Why? Because REST is just an architectural style. You can't bottle up that style. You can only understand it, and design your Web services in that style. (Analogous to the client-server architectural style. There is no client-server standard.)
While REST is not a standard, it does use standards:
HTTP
URL
XML/HTML/GIF/JPEG/etc (Resource Representations)
text/xml, text/html, image/gif, image/jpeg, etc (MIME Types) -
01 Aug 14
-
10 Jun 14
-
- Client-Server: a pull-based interaction style: consuming components pull representations.
- Stateless: each request from client to server must contain all the information necessary to understand the request, and cannot take advantage of any stored context on the server.
- Cache: to improve network efficiency responses must be capable of being labeled as cacheable or non-cacheable.
- Uniform interface: all resources are accessed with a generic interface (e.g., HTTP GET, POST, PUT, DELETE).
- Named resources - the system is comprised of resources which are named using a URL.
-
Interconnected resource representations - the representations of the resources are interconnected using URLs, thereby enabling a client to progress from one state to another.
-
Layered components - intermediaries, such as proxy servers, cache servers, gateways, etc, can be inserted between clients and resources to support performance, security, etc.
-
-
22 Apr 14
Terry KunyBuilding Web Services the REST Way
Pinboard rest restful development webservices xml restwebservice Delicious import
-
26 Feb 14
-
A representation of the resource is returned (e.g., Boeing747.html). The representation places the client application in a state. The result of the client traversing a hyperlink in Boeing747.html is another resource is accessed. The new representation places the client application into yet another state. Thus, the client application changes (transfers) state with each resource representation --> Representational State Transfer!
-
Here is Roy Fielding's explanation of the meaning of Representational State Transfer: "Representational State Transfer is intended to evoke an image of how a well-designed Web application behaves: a network of web pages (a virtual state-machine), where the user progresses through an application by selecting links (state transitions), resulting in the next page (representing the next state of the application) being transferred to the user and rendered for their use."
-
-
03 Feb 14
-
27 Jun 13
-
04 Jun 13
-
03 Jun 13
-
11 Jan 13
-
Create a URL to each resource. The resources should be nouns, not verbs. For example, do not use this:
-
-
12 Sep 12
-
09 Sep 12
-
A representation of the resource is returned (e.g., Boeing747.html). The representation places the client application in a state. The result of the client traversing a hyperlink in Boeing747.html is another resource is accessed. The new representation places the client application into yet another state. Thus, the client application changes (transfers) state with each resource representation --> Representational State Transfer!
-
-
12 Aug 12
-
09 Aug 12
-
13 Jul 12
-
19 Jun 12
-
13 Apr 12
-
14 Feb 12
-
04 Feb 12
-
05 Jan 12
-
21 Dec 11
-
15 Dec 11
-
30 Nov 11
-
26 Oct 11
-
20 Oct 11
-
10 Oct 11
-
07 Oct 11
-
28 Sep 11
-
26 Sep 11
-
REST is not a standard. You will not see the W3C putting out a REST specification. You will not see IBM or Microsoft or Sun selling a REST developer's toolkit. Why? Because REST is just an architectural style. You can't bottle up that style. You can only understand it, and design your Web services in that style. (Analogous to the client-server architectural style. There is no client-server standard.)
-
-
28 Aug 11
-
19 Aug 11
-
. No man/woman is an island. Likewise, no representation should be an island. In other words, put hyperlinks within resource representations to enable clients to drill down for more information, and/or to obtain related information.
-
-
20 Jul 11
-
I will first provide a brief introduction to REST and then describe how to build Web services in the REST style.
What is REST?
REST is a term coined by Roy Fielding in his Ph.D. dissertation [1] to describe an architecture style of networked systems. REST is an acronym standing for Representational State Transfer.Why is it called Representational State Transfer?
The Web is comprised of resources. A resource is any item of interest. For example, the Boeing Aircraft Corp may define a 747 resource. Clients may access that resource with this URL: <form action="">
</form>http://www.boeing.com/aircraft/747
-
-
09 Jul 11
-
08 Jul 11
-
28 May 11
-
11 May 11
-
03 May 11
-
26 Apr 11
-
REST Web Services Characteristics
-
Client-Server: a pull-based interaction style: consuming components pull representations.
-
Stateless: each request from client to server must contain all the information necessary to understand the request, and cannot take advantage of any stored context on the server.
-
Cache: to improve network efficiency responses must be capable of being labeled as cacheable or non-cacheable
-
Uniform interface: all resources are accessed with a generic interface (e.g., HTTP GET, POST, PUT, DELETE)
-
Named resources - the system is comprised of resources which are named using a URL.
-
Interconnected resource representations - the representations of the resources are interconnected using URLs, thereby enabling a client to progress from one state to another.
-
Layered components - intermediaries, such as proxy servers, cache servers, gateways, etc, can be inserted between clients and resources to support performance, security, etc.
-
-
25 Apr 11
julius beezerthis kind of stuff is the back end to all of googles h9 healthcare offering which I briefly perused this evening
-
23 Mar 11
-
03 Feb 11
-
29 Jan 11
-
25 Jan 11
-
01 Jan 11
-
29 Dec 10
-
- Here are the characteristics of REST:
- Client-Server: a pull-based interaction style: consuming components pull representations.
- Stateless: each request from client to server must contain all the information necessary to understand the request, and cannot take advantage of any stored context on the server.
- Cache: to improve network efficiency responses must be capable of being labeled as cacheable or non-cacheable.
- Uniform interface: all resources are accessed with a generic interface (e.g., HTTP GET, POST, PUT, DELETE).
- Named resources - the system is comprised of resources which are named using a URL.
- Interconnected resource representations - the representations of the resources are interconnected using URLs, thereby enabling a client to progress from one state to another.
- Layered components - intermediaries, such as proxy servers, cache servers, gateways, etc, can be inserted between clients and resources to support performance, security, etc.
-
-
23 Nov 10
-
24 Oct 10
-
19 Sep 10
-
03 Aug 10
-
07 Jul 10
-
05 Jun 10
-
03 Jun 10
-
13 May 10
-
26 Apr 10
-
23 Apr 10
-
22 Apr 10
-
15 Apr 10
-
14 Apr 10
-
13 Apr 10
-
09 Apr 10
-
31 Mar 10
-
26 Mar 10
-
Building Web Services the REST Way
-
REST - An Architectural Style, Not a Standard
-
Principles of REST Web Service Design
-
Specify the format of response data using a schema (DTD, W3C Schema, RelaxNG, or Schematron).
-
For those services that require a POST or PUT to it, also provide a schema to specify the format of the response.
-
Describe how your services are to be invoked using either a WSDL document, or simply an HTML document.
-
-
24 Mar 10
-
13 Mar 10
-
10 Mar 10
-
eb is a REST system! Many of those Web services that you have been using these many years - book-ordering services, search services, online dictionary services, etc - are REST-based Web services. Alas, you have been using REST, building REST services and you didn't even know it. REST is concerned with the "big picture" of the Web. It does not deal with implementation details (e.g., using Java servlets or CGI to implement a Web service). So let's look at an example of creating a Web service from the REST "
-
-
08 Mar 10
-
05 Mar 10
-
18 Feb 10
-
16 Feb 10
-
08 Feb 10
-
27 Jan 10
-
14 Jan 10
-
12 Jan 10
-
29 Dec 09
-
representation of the resource is returned
-
-
24 Dec 09
-
04 Dec 09
-
26 Nov 09
-
23 Nov 09
-
Parts Depot Web Services
-
-
19 Nov 09
-
13 Nov 09
-
26 Oct 09
-
25 Oct 09
-
01 Oct 09
Daniel IonescuThe representation places the client application in a state.
-
28 Sep 09
-
10 Sep 09
-
08 Sep 09
-
01 Sep 09
-
11 Aug 09
Andrius MazeikaREST is a term coined by Roy Fielding in his Ph.D. dissertation [1] to describe an architecture style of networked systems. REST is an acronym standing for Representational State Transfer.
-
06 Aug 09
-
26 Jul 09
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.