RE: Ideas: GETSRC & MULTIPUT

In general, I believe having distinct URL's for different resources
is far superior to defining new methods.  How would you set access
control on the "source" resource?  How would you get the properties of
the "source" resource?  If you have a URL for the source resource,
all this is straightforward ... but if you have something like a GETSRC
method, the only thing you can do with the "source" is get its content.

Cheers,
Geoff

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Monday, October 29, 2001 4:35 PM
To: Clemm, Geoff; WebDAV
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 Monday, 29 October 2001 16:55:42 UTC