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

RE: Ideas: GETSRC & MULTIPUT

From: Dylan Barrell <dbarrell@opentext.com>
Date: Tue, 30 Oct 2001 09:18:00 -0500
To: "Roy T. Fielding" <fielding@ebuilt.com>, "Jim Whitehead" <ejw@cse.ucsc.edu>
Cc: "WebDAV" <w3c-dist-auth@w3.org>
Message-ID: <NEBBIBDBCLDPAGPIKGMCEECEEFAA.dbarrell@opentext.com>
Transactions are overkill for this simple single operation.

I prefer a single put with a package made up of different parts - I don't
care what we call that.

--Dylan

> -----Original Message-----
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Roy T. Fielding
> Sent: Monday, October 29, 2001 5:25 PM
> To: Jim Whitehead
> Cc: WebDAV
> Subject: Re: Ideas: GETSRC & MULTIPUT
>
>
> On Mon, Oct 29, 2001 at 12:14:10PM -0800, Jim Whitehead wrote:
> > I'm interested in the list's thoughts on two ideas for DAV improvements:
> >
> > The first is to introduce a GETSRC method to support access to the
> > unprocessed source of a resource. This would decouple the
> dynamic response
> > of a resource (GET) from its static source (GETSRC).
>
> That would, of course, be completely contrary to the HTTP design and
> further propagate the mistake of not accessing properties as resources.
> Just use the source link.
>
> > The second is to introduce the MULTIPUT method to support "PUT with
> > PROPPATCH" scenarios. MULTIPUT would accept some subset of
> multipart MIME
> > packages and atomically write them to the server. This would support the
> > update of a resource and its metadata in one transaction.
>
> Please choose a better name -- MPUT and MULTIPUT means multiple
> PUT requests,
> which was already tried and abandoned.  Maybe you can call it
> PKG.  Or just
> define a mapping to transactions and leave them as separate requests.
>
> ....Roy
Received on Tuesday, 30 October 2001 09:19:07 GMT

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