Re: Bookmark 'stability'

Hi,

On Fri, Sep 28, 2012 at 10:46 AM, Ruben Verborgh
<[email protected]> wrote:
>> "Cool URIs don't change" is not a RESTful principle.
>
> If there’s no stability, how can a REST system possibly work?

In HTTP you can always redirect using the status codes:

301 Moved Permanently
302 Found
303 See Other
307 Temporary Redirect
308 Permanent Redirect (experimental)

Clients (that understand HTTP) can then make different decisions
depending on the type of redirect, like for example, updating a
bookmark (automatically or interactively with an end user).

This gives HTTP servers/applications the freedom to control their own
name space and a way to communicate those changes to HTTP clients.
Well behaved HTTP clients handle this intelligently.

Finally resources may actually disappear as part of the business logic
that the system supports. So requesting some URI:s will simply return
404 (Not Found) or 410 (Gone). Clients simply have to deal with that.

I think that HTTP "works" for the Web! ;-)

/Paul

-- 
Paul Cohen
www.seibostudios.se
mobile: +46 730 787 035
e-mail: [email protected]


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rest-discuss/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/rest-discuss/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/