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

Re: Ideas: GETSRC & MULTIPUT

From: Nicholas Atkinson <nik@casawana.com>
Date: Tue, 30 Oct 2001 16:31:07 -0000
Message-ID: <004001c16161$50c3b650$0300000a@natkinwkstn>
To: "WebDAV" <w3c-dist-auth@w3.org>
Hi there

Is there any documentation available which describes what Microsoft are
doing with their Translate Header?  (I have tried the archive of this list
but the search facility is not working).

Does the Apache web server support something similar?

nik

----- Original Message -----
From: "Julian Reschke" <julian.reschke@gmx.de>
To: "Clemm, Geoff" <gclemm@rational.com>; "WebDAV" <w3c-dist-auth@w3.org>
Sent: 29 October 2001 21:35
Subject: RE: Ideas: GETSRC & MULTIPUT


> Geoff,
>
> I'd like to see how the DAV:dst in WebDAV can support what Microsoft is
> doing with their Translate header (namely, having the source and the
dynamic
> content at the same URL).
>
> See also my comments in
>
> <http://lists.w3.org/Archives/Public/w3c-dist-auth/2001JulSep/0149.html>
>
> Julian
>
> > -----Original Message-----
> > From: w3c-dist-auth-request@w3.org
> > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Clemm, Geoff
> > Sent: Monday, October 29, 2001 10:18 PM
> > To: WebDAV
> > Subject: RE: Ideas: GETSRC & MULTIPUT
> >
> >
> > Why isn't GETSRC just a GET on the DAV:dst of the DAV:source property?
> > (If it is just a shorthand for this, I'm against the redundant
marshalling
> > of this request through a new method).
> >
> > As for MULTIPUT, that sounds fine to me, but it should be accompanied by
> > a MULTIGET, which would allow reading of a resource and its metadata in
> > one transaction.
> >
> > Cheers,
> > Geoff
> >
> > -----Original Message-----
> > From: Jim Whitehead [mailto:ejw@cse.ucsc.edu]
> > Sent: Monday, October 29, 2001 3:14 PM
> > To: WebDAV
> > Subject: Ideas: GETSRC & MULTIPUT
> >
> >
> > 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).
> >
> > 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.
> >
> > - Jim
> >
>
Received on Tuesday, 30 October 2001 11:39:17 GMT

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