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


From: Roy T. Fielding <fielding@ebuilt.com>
Date: Mon, 29 Oct 2001 16:21:57 -0800
To: Jim Whitehead <ejw@cse.ucsc.edu>
Cc: WebDAV <w3c-dist-auth@w3.org>
Message-ID: <20011029162157.A8666@waka.ebuilt.net>
> The source link didn't work. Telling people to use the source link is not,
> IMO, productive.

Under what conditions did it not work?  Do you mean just never implemented?

> GETSRC could be defined as something like, "returns to the client a
> representation of the resource suitable for editing in an authoring client",
> so we avoid issues of getting at the "true" state of the resource. GETSRC
> wouldn't have the same caching properties as GET; I don't see that as being
> a big problem for authoring.
> So, which specific HTTP design principle(s) does this proposal violate?

The one that calls for different resources to be accessed using different URI.
The set of source URI for some other URI are different resources.  Since
there can be many more than one source per representation, the notion of
creating a new method to avoid one indirection is just wrong.

Received on Monday, 29 October 2001 19:24:46 UTC

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