4 ms·
So in reading that chapter it seems like REST can be boiled down to these statements: 1) Client-server 2) Stateless 3) Cacheable or noncacheable constraints
by kenjackson 16y ago
So in reading that chapter it seems like REST can be boiled down to these statements:
1) Client-server
2) Stateless
3) Cacheable or noncacheable constraints
4) Uniform interface
5) Abstracted so that you can only see the layers directly in front of you.
6) Client side code, e.g., Javascript
7) (Potentially) Late binding of reference to representation
8) "The connector interface is similar to procedural invocation, but with important differences in the passing of parameters and results. The in-parameters consist of request control data, a resource identifier indicating the target of the request, and an optional representation. The out-parameters consist of response control data, optional resource metadata, and an optional representation."
But a lot of what is described as REST imposes additional constraints that I don't see in this description. Did I miss something?
- collint 16y agoI tend to agree with you, but don't just take it from me: http://tech.groups.yahoo.com/group/rest-discuss/message/6735 http://tech.groups.yahoo.com/group/rest-discuss/message/6735 I don't think it's fair to say the original dissertation is the final word on REST, but I do think almost all of the discussion on REST is way off target. It feels like almost all the discussion is about the construction of URLs. REST has become a buzzword, people use it just to project credibility.
- deleted 16y ago[deleted]
- T-R 16y agoI have a lot of respect for him, but it's pretty disappointing to see him so opposed to doing things that would bring more clarity to those trying to understand his work. This is at least the third quote I've seen of him blowing off the idea of giving examples or more documentation. It's further disappointing to see "that document is my dissertation" juxtaposed with "I sometimes need to expand on the terse explanations provided in the dissertation, because I was in a hurry when I wrote it".
- deleted 16y ago[deleted]
- T-R 16y agoOne (additional?) constraint that perhaps doesn't fall nicely into one of those categories is "Hypermedia as the Engine of Application State" (HATEOAS), which was emphasized (though not with those exact words) by Roy Fielding on his blog: http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...
- AffableSpatula 16y agoIt's part of the uniform interface constraint http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_5 http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch...