W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2004

Re: redirect references protocol: automatic update

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Fri, 9 Jan 2004 08:45:19 -0500
To: " webdav" <w3c-dist-auth@w3.org>
Message-ID: <OF72D14D10.45626C98-ON85256E16.004B674F-85256E16.004B87FF@us.ibm.com>

I prefer (3), a simple singe resource type, with the other information 
moved into a set of properties.

Cheers,
Geoff

Julian wrote on 01/09/2004 07:46:41 AM:

> 
> Geoffrey M Clemm wrote:
> > One possibility is to have an additional argument to MKREDIRECTREF,
> > e.g. DAV:stable, that means that the client forbids the server from
> > auto-updating the reference.  A client that doesn't care would leave
> > off this parameter, and the server would do what it wanted, while a
> > client that cared would specify this parameter, and a server that 
doesn't
> > support stable redirectref's would fail the request.
> 
> Yep.
> 
> The thing I'm currently unsure about is how to model the different 
> properties of a link (stability, response status). Several approaches 
> come to mind:
> 
> 1) different resource types (redirect-301, redirect-302, ...)
> 
> 2) one resource type with extension elements, such as
> 
>    <redirect-ref><status301/><stable/></redirect-ref>
> 
> 3) one simple resource type with the remaining information moved into 
> separate properties (like it was proposed for the status).
> 
> Regards, Julian
> 
> -- 
> <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
> 
Received on Friday, 9 January 2004 08:48:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:17:51 UTC