Re: Bookmark 'stability'
Paul Cohen <[email protected]>
| Newsgroups | gmane.comp.web.services.rest |
|---|---|
| Message-ID | <CAA1Y72HEKnddZ9kNaPcZmZaK-fELZaML3dpvonZ1cGK5a7a8FQ@mail.gmail.com> |
On Mon, Oct 8, 2012 at 1:03 PM, Eric J. Bowman <[email protected]> wrote: > Paul Cohen wrote: >> >> My understanding of coupling in the context of data types is quite the >> opposite! Also I don't see that REST deals with data types at all - >> standardized or not. >> > > OMG, standardized media types are a key concept of REST, Yes indeed. But media types /= data types. The web works fine without being recompiled every morning. >> I don't think you understood what I meant. I used the term "coupling" >> in the sense that this client requirement on the server (of >> maintaining URI:s) leads to undesired consequences for the developers >> and the server. >> > > Client requests old URL. Server responds 308 with new URL. Client > updates bookmark, never requests obsolete URL again. There is no > coupling here, by any definition of the term. I am not arguing against that this is good behaviour on the part of the server. I'm saying that there should be no formal requirement for a server to maintain (for ever) all URI:s that have been exposed to clients. We don't seem to have the same understanding of the terms involved or problem, so I'm leaving the discussion for now. /Paul -- Paul Cohen www.seibostudios.se mobile: +46 730 787 035 e-mail: [email protected]