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


From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 31 Oct 2001 01:33:12 +0100
To: "Roy T. Fielding" <fielding@ebuilt.com>, "Eric Sedlar" <eric.sedlar@oracle.com>
Cc: "WebDAV" <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCGENNDFAA.julian.reschke@gmx.de>
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Roy T. Fielding
> Sent: Wednesday, October 31, 2001 1:23 AM
> To: Eric Sedlar
> Cc: WebDAV
> Subject: Re: GETSRC & MULTIPUT
> On Tue, Oct 30, 2001 at 12:19:27PM -0800, Eric Sedlar wrote:
> > The fundamental question that must be addressed is whether or
> not the source
> > resource and the output resource are the same.  To me, the
> question boils
> > down to wanting to have symmetry in my methods.  If I call
> > then use PROPFIND to see the properties I just wrote.  We need the same
> > thing for PUT.  If I call PUT on a URL, I want a method that
> gets me back
> > the stuff I just PUT at that URL.
> GET already provides that -- if you can successfully invoke PUT on a
> resource, then a GET on that same resource will be the stuff that you PUT
> (assuming no other actions occurred in-between).
> However, PUT is not allowed on many resources, specifically those
> resources
> that only exist as a synthesis of other resources.  The source
> links, which
> were present in the original HTTP/1.1 proposal and later transformed into
> a property in 2518, tell the client how it can edit that resource
> given that
> authoring on the same URI is not possible, period.

Well, that's interesting to know, but -- from looking at RFC2518 this is
just "hear-say". What you say makes sense, but it's certainly not what
RFC2518 says (or doesn't say: that when a resource has a source property it
can't be PUT to).
Received on Tuesday, 30 October 2001 19:32:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:24 UTC