3 ms·
It's not really REST if there's no link in sight. Why not just call it a HTTP API or a Webservice?
by treve 9y ago
It's not really REST if there's no link in sight. Why not just call it a HTTP API or a Webservice?
- Waterluvian 9y agoThe REST train left the station a long time ago without HATEOAS on it. Let's just move on; I don't think there's much value left in that worn out debate.
- jbenner-radham 9y agoWhat are you referring to when you say “no link in sight” in regards to REST?
- axlee 9y agoBasically, instead of having a "User" response built like this: User { name: "Bob" id: 1 } You would have something like this: User { name: "Bob" href: "http://www.example.com/api/users/1" }
- gabrielcsapo 9y agoThis kind of reminds me of hateoas. [1] [1] https://spring.io/understanding/HATEOAS https://spring.io/understanding/HATEOAS
- o1lab 9y agoThank you for your input. I will consider this feature going ahead.
- jbenner-radham 9y agoIsn’t that HATEOAS and not REST specifically? I don’t remember anything in Roy Fielding’s dissertation specifying any type of response body.
- nilved 9y agoHypermedia as the Engine of Application State
- JimDabell 9y agoREST APIs must be hypertext-driven: http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...
- jbenner-radham 9y agoThank you for that link. I’ve read through Roy’s original dissertation but apparently missed some of the details. This post helps clarify things.
- jack9 9y agoREST does not require a specific response. The original paper used specific verb as an example present in the wild, which has oft been misinterpreted as required usage. Formatted summary - http://www.ics.uci.edu/%7Efielding/pubs/dissertation/rest_arch_style.htm http://www.ics.uci.edu/%7Efielding/pubs/dissertation/rest_ar... - "The most frequent form of request semantics is that of retrieving a representation of a resource (e.g., the "GET" method in HTTP), which can often be cached for later reuse." A critique of HTTP REST - http://cafe.elharo.com/web/why-rest-failed/ http://cafe.elharo.com/web/why-rest-failed/ - "Representational State Transfer (REST) is the explicit architecture of HTTP and the World Wide Web" which is a notably incorrect statement. Other interesting articles: http://www.artima.com/lejava/articles/why_put_and_delete.html http://www.artima.com/lejava/articles/why_put_and_delete.htm... http://roy.gbiv.com/untangled/2009/it-is-okay-to-use-post http://roy.gbiv.com/untangled/2009/it-is-okay-to-use-post