News for hackers. Stuff that matters.
Re:REST in peace, SOAP by barrkel on Friday October 15, 2010 @02:30PM (#1795633)
It's really simple: consider documents retrieved by requests to be nodes in a state machine, and consider hyperlinks in the documents to be directed edges to other nodes. That's it: your state is your position in the state machine, and your state transitions are navigation through the web of hyperlinks.

If you have an API which talks about URI patterns, for example, then it's not REST in this sense, because these URI patterns aren't found inside the documents as hyperlinks. Instead, they're found outside the document.

Similarly, if state is not encoded and transformed by following links in the web of documents, and instead is implicitly understood to be occurring whenever you do e.g. a PUT of some URI pattern, then hypermedia isn't the engine of application state.

A purist approach to REST, though, is IMO impractical for systems that aren't very like the web itself.

There are no comments on this comment yet.