Ben Ramsey ■ OCPHP/LAPHP Meeting ■ 24 Sep 2009 Intro to REST 

REST Roatan Beach - Perfect Day, by Janusz Leszczynski 

Tom Coates, by Patrick Lauke Is it about pretty URLs? 

Web Developer Gang Sign, by Josh Lewis How about XML over HTTP? #webdevgangsign 

A Bar of Ivory Soap, by iirraa Any web service that’s not SOAP? 

Representational State Transfer Restful Summer, by Clear Inner Vision 

REST defines a style by which a resource’s state may be transferred using a representation of that resource. REST defines a style by which a resource’s state may be transferred using a representation of that resource. REST defines a style by which a resource’s state may be transferred using a representation of that resource. 

Client-server Separated, by Hansol Lee 

Stateless Stateless by Koesmanto Bong 

Cache Cache County, Utah by J. Stephen Conn 

used to interface, by Tom Hensel Uniform Interface 1.Identification of resources 2.Representation of resources 3.Linked resources 4.Resource metadata 

Layered Sedimentary Layers by Mark Thurman 

Code-on-demand jeremy’s tie by Gitchel 

Sand Banks Sunset, by Clear Inner Vision RESTful Benefits Improved response time & reduced server load Improves server scalability Requires less client-side software Depends less on vendor software No need for resource discovery Better long-term compatibility & evolvability than RPC 

Drip Drops and the Spider Web, by Mike Bitzenhofer “[REST] 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.” 
 — Roy Fielding 

Hypertext Transfer Protocol #110 Hypertext Transfer Protocol, by maako URIs provide unique addresses Constrained interface with methods and content types Transactions are atomic Built-in support for layering Provides for cache control 

HTTP Interface #110 Hypertext Transfer Protocol, by maako Methods GET PUT POST DELETE Cut & Paste Copy Paste Over Paste After Cut 

Content Types #110 Hypertext Transfer Protocol, by maako HTTP supports content types through the Content-Type header A single resource can be transferred in various content types Content negotiation used to tell the server what type to return to the client REST community doesn’t care for content negotiation 

Let’s see it in action 

GET / HTTP/1.1 Host: atom.example.org HTTP/1.x 200 OK Date: Mon, 21 Sep 2009 16:33:45 GMT Content-Type: application/atomsvc+xml 

Our Content Store Users application/atom+xml;type=entry Content application/atom+xml;type=entry 

GET /user HTTP/1.1 Host: atom.example.org HTTP/1.x 200 OK Date: Mon, 21 Sep 2009 16:34:26 GMT Content-Type: application/atom+xml 

Users 2009-09-21T05:21:19Z tag:example.org,2009-09:user Users application/atom+xml;type=entry ... 

Manipulate a user 

GET /user/ramsey HTTP/1.1 Host: atom.example.org HTTP/1.x 200 OK Date: Mon, 21 Sep 2009 16:34:26 GMT Content-Type: application/atom+xml;type=entry 

ramsey ramsey tag:example.org,2008:user/ramsey 2009-09-21T13:45:00Z 2008-05-23T16:23:34Z 

ramsey ramsey tag:example.org,2008:user/ramsey 2009-09-22T09:14:58Z 2008-05-23T16:23:34Z 

PUT /user/ramsey HTTP/1.1 Host: atom.example.org Content-Type: application/atom+xml;type=entry {body here} HTTP/1.x 200 OK Date: Mon, 22 Sep 2009 09:14:59 GMT Content-Type: application/atom+xml;type=entry 

Add some content 

Perfect Mark Phelps tag:example.org,2009:content/perfect 2009-09-22T20:12:08Z TWFuIGlzIGRpc3Rpbmd1aXNoZWQsIG5vdCBvbmx5IGJ5IGhpcyByZWF IHNpbmd1bGFyIHBhc3Npb24gZnJvbSBvdGhlciBhbmltYWxzLCB3aGl ... 

POST /content HTTP/1.1 Host: atom.example.org Content-Type: application/atom+xml;type=entry {body here} HTTP/1.x 202 Accepted Date: Mon, 22 Sep 2009 09:14:59 GMT {body contains status indicator} 

Questions? benramsey.com 

Intro to REST Copyright © Ben Ramsey. Some rights reserved. This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License. For uses not covered under this license, please contact the author.