Re: Bookmark 'stability'
Steve Klabnik <[email protected]>
| Newsgroups | gmane.comp.web.services.rest |
|---|---|
| Message-ID | <CABL+ZB4f+YG=C44kpSJRG=R0rOC-KCt+-ZhbuE=RfCR4vtZg=A@mail.gmail.com> |
> Maintaining obsolete URIs is not an example of "coupling" as applies to > REST. It is an incredibly clear violation of servers controlling their own namespace. Seriously. I don't even know why this is contentious. > A REST API must not define fixed resource names or hierarchies (an obvious coupling of client and server). Servers must have the freedom to control their own namespace. Instead, allow servers to instruct clients on how to construct appropriate URIs, such as is done in HTML forms and URI templates, by defining those instructions within media types and link relations. [Failure here implies that clients are assuming a resource structure due to out-of band information, such as a domain-specific standard, which is the data-oriented equivalent to RPC's functional coupling]. http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven