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

Re: remaining redirect ref issues

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Thu, 20 Nov 2003 09:30:25 -0500
To: w3c-dist-auth@w3.org
Message-ID: <OFEAEDA909.84A86A62-ON85256DE4.004F50FB-85256DE4.004FAD16@us.ibm.com>
Below I expressed a general problem with the "authoring URI" approach
and Depth operations.  In this particular case (i.e. redirect reference
resources), there is the additional problem that I can't use PROPFIND
to find out the "authoring URI" (because the redirect reference will
automatically redirect the PROPFIND request away from the redirect 
resource).
So I'd need to define a GET-REDIRECT-AUTHORING-URI method to find out
the authoring URI (and then have the problem described in my original
message :-).  The header approach is looking better and better (:-).

Cheers,
Geoff

Geoff wrote on 11/18/2003 09:53:32 PM:

> 
> In principle, I agree with Roy on this issue. 
> 
> But a problem with the "authoring URI" approach occurs when you want to 
> apply a Depth operation (e.g. PROPFIND).  You can get all the authoring 
> URIs with a single Depth PROPFIND, but then how do you avoid having to 
> apply the operation separately to each of the authoring URIs? 
> 
> In the case of PROPFIND, there is a solution provided by RFC-3253 
> (the DAV:expand-property REPORT), but that only works for PROPFIND, 
> not for other Depth methods like COPY. 
> 
> Cheers, 
> Geoff 
> 
> Roy wrote on 11/12/2003 01:08:34 PM:
> 
> > I am certain I have said this before, though it was several years ago.
> > The RESOURCE IS NOT A STORAGE ITEM ON THE SERVER!  Failure to get 
> > straight
> > on that one bit is what causes webdav to trip over HTTP whenever it
> > tries to "author" anything other than a boring old file.
> > 
> > In this case, there must be two different URIs -- one for the resource
> > and one for the configuration of that resource.  That configuration
> > may be as simple as a URI, maybe a status code and a URI, or maybe 
even
> > an XML document -- that is what must be defined by the redirect 
> > protocol.
> > The actual URI which responds to requests with a redirect should have 
a
> > link to its configuration URI, such that an authoring tool can 
discover
> > the authorable resource that causes this resource to redirect.  That 
is
> > why webdav requires a source link in order to perform HTTP authoring.
> > 
> > The same principle holds for all dynamic content.
> > 
> > ....Roy
> > 
Received on Thursday, 20 November 2003 09:30:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:05 GMT