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

Source header instead of property? (was Re: A case for GETSRC (or other mechanism to that effect))

From: Erik Seaberg <erk@flyingcroc.com>
Date: 28 Feb 2002 20:41:22 -0800
To: w3c-dist-auth@w3c.org
Message-ID: <86heo0vr0t.fsf_-_@unx51.staff.flyingcroc.net>
The only reason for GETSRC or "Translate: F" is to overload one URI for
both the source and output resources, but it seems to me that breaks a
lot of features.  We suddenly need to duplicate most properties
({DAV:}getsrcetag, {DAV:}getsrccontenttype...) to deal well with caching
and editing.  You're likely to go through content negotiation and wind
up editing just one variant without even realizing it (or worse, store
one variant at the vanilla URI's corresponding filename and inhibit
negotiation!).  And Web development being the way it is, it's almost
certain that when GETSRC seems to usually work on simplistic servers,
hardly any clients will know how to use {DAV:}source in the cases where
it won't.

But if the output resource does have a separate URI, a PUT or LOCK or
PROPPATCH on it probably doesn't make sense, so it's not likely that
many modules will bother being compliant enough to answer a PROPFIND
request for {DAV:}source (in my case, GET clients and DAV clients are
talking to different servers entirely).  An HTTP header containing the
source URIs for an output resource (only for authenticated requests?)
should be much easier to implement; would that be more likely to be
widely adopted and used?
Received on Thursday, 28 February 2002 23:43:57 UTC

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