Timeline for answer to How to provide a service with RESTful API? by sea-rob

Current License: CC BY-SA 3.0

Post Revisions

6 events

when toggle format	what		by	license	comment
Apr 24, 2014 at 2:38	vote	accept	Victor Ronin
Apr 23, 2014 at 22:53	comment	added	sea-rob		@user61852 I should say, that's the ideal. I've only been on 1 team that actually implemented that. That's why I usually just say "JSON over HTTP" instead of "REST". Maybe "Resource-oriented service". Also, a lot of times, if you take the REST buzzword out of a conversation, the answer becomes clear.
Apr 23, 2014 at 22:48	comment	added	sea-rob		That gets pretty deep. Most people making "REST" interfaces are really just making JSON over HTTP interfaces, because they're missing a central concern: passing hypermedia that tells a client how to modify the state of the resource. In HTML, think of `<img>` tags or `<form>` tags. Those are hypermedia, and contain links. In order to meet the basic criterion for REST ;) a RESTful service must return links that tell the client how to modify the resource, or fetch more data. You can't communicate the links "out of band". Look up HATEOAS for more info; there is a lot of discussion out there.
Apr 23, 2014 at 21:58	comment	added	Tulains Córdova		Please explain "URIs the client uses should come from hypermedia".
Apr 23, 2014 at 18:01	comment	added	Calphool		Yeah, I agree with Rob Y. Basically REST applies the HTTP verbs to all actions, and begs a question to all of us OOAD people. What would we do if we were limited to about 4 or 5 methods per class, and they all had to be the same? The answer seems to be "Hey, I didn't realize I could get by without all these different methods (verbs) if I just broke down the noun (class) nomenclature better in my design!" It seems to be that you can break down these relationships almost ad infinitum, and when you do, POST, GET, DELETE, etc. seem adequate.
Apr 23, 2014 at 16:45	history	answered	sea-rob	CC BY-SA 3.0