W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2003

RE: redirect ref spec, update on issue lc-85-301

From: Lisa Dusseault <lisa@xythos.com>
Date: Fri, 17 Oct 2003 23:45:23 -0700
To: "'Julian Reschke'" <julian.reschke@gmx.de>, <w3c-dist-auth@w3.org>
Message-ID: <001701c39543$6864a680$f8cb90c6@lisalap>

> For now I propose that the client is able to specify the 
> redirection type as a resource type, such as 
> "DAV:permanent-redirect-reference" and 
> "DAV:temporary-redirect-reference". This spec would only 
> define the behaviour for these two resource types and would 
> allow future extensions using new resource types and 
> suggested response codes.

What's the use case for this functionality.  How would a user
creating a link decide whether this was a permanent or a temporary
redirect link?  Is anybody actually planning to implement a 
client that would care which one it was creating?  

If there aren't implementation plans, use case, etc, then the
KISS principle suggests that we pick one. Since redirect resources
are in fact permanent until deleted (the temporariness is 
completely unknown), I see no reason why they 
wouldn't all be the same kind of redirect resource.

Before we chose one HTTP response or another, it would be good 
to know whether HTTP clients behave differently. I have no data
on this.  

Received on Friday, 17 October 2003 14:48:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:28 UTC