Fielding Dissertation: CHAPTER 5: Representational State Transfer (REST)

This link has been bookmarked by 42 people . It was first bookmarked on 02 Mar 2006, by Jeff Schilling.

23 Oct 09

andy cary
- Client-Server
  
  The first constraints added to our hybrid style are those of the client-server architectural style (Figure 5-2), described in Section 3.4.1. Separation of concerns is the principle behind the client-server constraints. By separating the user interface concerns from the data storage concerns, we improve the portability of the user interface across multiple platforms and improve scalability by simplifying the server components. Perhaps most significant to the Web, however, is that the separation allows the components to evolve independently, thus supporting the Internet-scale requirement of multiple organizational domains.
- Stateless
  
  We next add a constraint to the client-server interaction: communication must be stateless in nature, as in the client-stateless-server (CSS) style of Section 3.4.3 (Figure 5-3), such that each request from client to server must contain all of the information necessary to understand the request, and cannot take advantage of any stored context on the server. Session state is therefore kept entirely on the client.
- 7 more annotations...
- - Cache
    
    In order to improve network efficiency, we add cache constraints to form the client-cache-stateless-server style of Section 3.4.4 (Figure 5-4). Cache constraints require that the data within a response to a request be implicitly or explicitly labeled as cacheable or non-cacheable. If a response is cacheable, then a client cache is given the right to reuse that response data for later, equivalent requests.
  - The advantage of adding cache constraints is that they have the potential to partially or completely eliminate some interactions, improving efficiency, scalability, and user-perceived performance by reducing the average latency of a series of interactions. The trade-off, however, is that a cache can decrease reliability if stale data within the cache differs significantly from the data that would have been obtained had the request been sent directly to the server.
  - Uniform Interface
    
    The central feature that distinguishes the REST architectural style from other network-based styles is its emphasis on a uniform interface between components
  - Layered System
    
    In order to further improve behavior for Internet-scale requirements, we add layered system constraints (Figure 5-7). As described in Section 3.4.2, the layered system style allows an architecture to be composed of hierarchical layers by constraining component behavior such that each component cannot "see" beyond the immediate layer with which they are interacting.
  - Intermediaries can also be used to improve system scalability by enabling load balancing of services across multiple networks and processors.
  - Placing shared caches at the boundaries of an organizational domain can result in significant performance benefits [136]. Such layers also allow security policies to be enforced on data crossing the organizational boundary, as is required by firewalls
  - Code-On-Demand
    
    The final addition to our constraint set for REST comes from the code-on-demand style of Section 3.5.3 (Figure 5-8). REST allows client functionality to be extended by downloading and executing code in the form of applets or scripts. This simplifies clients by reducing the number of features required to be pre-implemented. Allowing features to be downloaded after deployment improves system extensibility. However, it also reduces visibility, and thus is only an optional constraint within REST.
28 Sep 09

Ben Dembroski
rest web programming webservices fielding reference development
30 Aug 09

alfred westerveld
23 Jul 09

Philipp Heinemann
WebApplication rest architecture web webservices programming http design
21 Jul 09

martinchilvers
rest web
19 Jul 09

maverick_blr
rest design
24 Mar 09

sven duzont
19 Dec 08

Javier Neira
reference rest
16 Dec 08

Satheesh Kumar Mohan
webservices reference rest
07 Nov 08

Scott Reynolds
rest
22 Oct 08

Tim Bunce
Programming - APIs
18 Aug 08

Vinay R
rest
takayuki kawamoto
xml webservices REST
17 Aug 08

Frank Colcord
Ruby
13 Aug 08

Bhaskar Ghosh
Bookmarks_Menu RestFul_Web_Services rest architecture web webservices programming http design
01 Apr 08

David Alfaro
rest soa woa
19 Jan 08

DJHell .
Dissertation Representational State Transfer Rest Roy Thomas Fielding development
21 Nov 07

Terry Borden
IBM CODE etc. Web 2.0
06 Aug 07

Mats Svensson
REST programming useful webdev
02 Jun 07

Ken Wei
design fielding rest
02 May 07

Stuart Laughlin
- This chapter introduces and elaborates the Representational State Transfer (REST) architectural style for distributed hypermedia systems, describing the software engineering principles guiding REST and the interaction constraints chosen to retain those principles, while contrasting them to the constraints of other architectural styles. REST is a hybrid style derived from several of the network-based architectural styles described in Chapter 3 and combined with additional constraints that define a uniform connector interface. The software architecture framework of Chapter 1 is used to define the architectural elements of REST and examine sample process, connector, and data views of prototypical architectures.
12 Jan 07

Arrix Z
rest
11 Dec 06

taylor parsons
deli rest
27 Nov 06

Matti Narkia
rest web architecture webservices programming design http Fielding Dissertation specification documentation doc reference science research imported delicious
24 Nov 06

Todd Sayre
imported:del.icio.us rest
09 Aug 06

J S
27 Jul 06

Yar Eeh
design web
25 Jul 06

Jeff Schilling
rest web-services
10 Jul 06

David Corking
Web development
- Additional constraints can then be applied to form a new architectural style that better reflects the desired properties of a modern Web architecture. This section provides a general overview of REST by walking through the process of deriving it as an architectural style.
21 Jun 06

Jaroslaw Zabiello
programming rest
23 Oct 05

M G
06 Oct 05

David Wiley
At last, a decent explication of this whole REST thing.

rest web
22 May 05

Jonathan Broad
rest
01 Mar 05

Heinz Wittenbrink
This chapter introduces and elaborates the Representational State Transfer (REST) architectural style for distributed hypermedia systems, describing the software engineering principles guiding REST

medientheorie basisliteratur by:RoyFielding
06 Nov 03

Nicolas Hoizey
Veille Intégration REST Web Services