Tag: REST

REpresentational State Transfer

Tag: REST

REpresentational State Transfer

Tag: REST

REpresentational State Transfer

Hypermedia as the Engine of Application State

One of the least well understood core tenets of the REST architectural style is that “hypermedia is the engine of application state”. Which basically means that responses from the server will be documents that include URIs to everything you can do next. For example, if GET a blog post the response document will have URIs

Continue Reading…

Tag: REST

REpresentational State Transfer

Tag: REST

REpresentational State Transfer

RESTful resource creation (redux)

Benjamin Carlyle has posted a followup about using PUT to create new resources in which he brings up some interesting issues. First, it seems I miss understood his original idea slightly. My misunderstanding does not affect how I feel about his approach much. I don’t like the idea of PUT-ting to a “factory” resource with

Continue Reading…

Tag: REST

REpresentational State Transfer

Tag: REST

REpresentational State Transfer

Deprecating POST

Benjamin Carlyle has an interesting bit about the possibility of deprecating the HTTP POST method. I think most people who have thought deeply about RESTful architectures have had similar thoughts. GET, PUT and DELETE are all nicely idempotent, but POST is not. GET, PUT, and DELETE have clean, well defined semantics, but POST does not.

Continue Reading…

Tag: REST

REpresentational State Transfer

Peter’s WOA Maxims — #17

Never provide representations of static resources by dynamic means. Or, serve anything you possibly can directly from a file on a local file system. There are several reasons for avoiding dynamic mechanisms whenever possible. The most obvious reason is that it is wasteful to generate the identical content repeatedly. If the resource never, or very

Continue Reading…

Tag: REST

REpresentational State Transfer

Tag: REST

REpresentational State Transfer