Re: Bookmark 'stability'

Paul Cohen wrote:
> 
> A server should commit itself to some "official URI:s", or entry
> points. But forcing a server to commit itself to maintaining all URI:s
> that have ever been published to any client seems to me like
> introducing unneccesary coupling.
> 

How is this coupling?  I take over a website for a client, change the
URI allocation scheme, then set up redirection on UltraDNS.  Since REST
is a layered architecture, maintaining obsolete URIs doesn't even have
to be part of the new system.  It's a courtesy to users, but even that
isn't a requirement.  Installing a new system using new URIs is *not* a
REST violation, even if the old links die outright, the 404 response
can include a search interface or link to the new homepage, meeting the
hypertext constraint -- again, how is this coupling?

-Eric