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 [email protected], Anne Thomas Manes <atma...@...> 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
