REST vs Web: Resource identifier -- URI Standard media type -- MIME Uniform interface -- HTTP or a mapping of HTTP method semantics to other protocols
When Roy says REST works over file, FTP, gopher, the point is that the protocol is immaterial so long as the semantics of interaction are uniform. eg. GET, POST, etc are generic by definition. Cheers Stu Sent from my iPad On 2010-04-07, at 12:13 PM, Michael Poulin <[email protected]> wrote: I see an analogy... in SOAP and Web Services. SOAP is not a mandatory protocol for Web Services as well. Ok, HTTP is optional, how about URI? It seems that a form of URI is a mandatory for resource access mechanism... - Michael From: reamon943 <[email protected]> To: [email protected] Sent: Wed, April 7, 2010 5:26:12 PM Subject: [service-orientated-architecture] Re: You on iPads Found this post from Fielding @ http://tech. groups.yahoo. com/group/ rest-discuss/ message/3320 "Good grief. Why does everyone equate REST with HTTP? REST apps work quite well with file, ftp, gopher, wais, urn, ... I won't even mention waka in that list because it isn't done yet." -Rob --- In service-orientated- architecture@ yahoogroups. com, "reamon943" <rea...@...> wrote: > > I'm with Steve on this one. REST is not simply HTTP and URIs. HTTP is but one > protocol that can be used for RESTful interactions. REST does not prescribe > the use of HTTP. The mere use of HTTP does not indicate an app is following > REST principles. There are plenty of opportunities to use HTTP in non-RESTful > ways. > > -Rob > > --- In service-orientated- architecture@ yahoogroups. com, Anne Thomas Manes > <atmanes@> wrote: > > > > Responding to this specific comment: > > > > "HTTP and URI (which isn't REST) " > > > > > > Well, actually, HTTP and URI *is* REST. Or at least it's the essence of > > REST. All interfaces, all interesting bits of information, all interactions, > > and all application workflow in a RESTful application are driven by HTTP and > > URIs. As Stefan Tilkov says, REST is using HTTP as it was intended. > > > > REST is: > > > > - Everything of interest has an identifier and the format of those > > identifiers is uniform (e.g., a URI) > > - Every identified resource supports a uniform API (e.g., HTTP methods) > > - The application uses hypermedia to coordinate application state and the > > process flow (HATEOAS) > > > > REST is entirely about HTTP and URIs. > > > > If you intend to support the iPad as a UI device for your service, you > > should design the service so that client applications can interact with it > > using HTTP and URIs. > > > > Anne > __________________________________________________________________ Make your browsing faster, safer, and easier with the new Internet Explorer® 8. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/
