Re: [caldav] Write-up draft-reschke-webdav-post-05

Julian Reschke <julian.reschke@gmx.de> Sun, 17 January 2010 21:21 UTC

Message-ID: <4B537F34.2030704@gmx.de>
Date: Sun, 17 Jan 2010 22:20:52 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Mike Douglass <douglm@rpi.edu>
References: <0275B11A464404216CDC3B56@socrates.local> <4B5378A7.2010504@rpi.edu>
In-Reply-To: <4B5378A7.2010504@rpi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: CalDAV <caldav@ietf.org>, WebDAV <w3c-dist-auth@w3.org>, CardDAV <vcarddav@ietf.org>
Subject: Re: [caldav] Write-up draft-reschke-webdav-post-05
Precedence: list

Mike Douglass wrote:
> I expect I will implement this in the near future and from my reading
> would support the approach of submitting as a proposed standard.
> 
> A question raised by the proposal:
> Is there any intent to provide an equivalent for COPY and MOVE? This
> proposal seems to handle the case of symlinked resources but COPY and
> MOVE would still be an issue.

This has been discussed before.

Using POST to add collection members is straigthforward, after all, this 
was what POST was defined to do in the first place. So this 
specification just allows servers to expose support for something they 
could have done all the time.

The problem is that extending this to methods other than PUT *very* 
quickly makes it very complicated, as the namespace operations also 
require Depth header support.

BTW: why "symlinked"?

BR, Julian

[caldav] Write-up draft-reschke-webdav-post-05 Cyrus Daboo
Re: [caldav] Write-up draft-reschke-webdav-post-05 Mike Douglass
Re: [caldav] Write-up draft-reschke-webdav-post-05 Julian Reschke
Re: [caldav] Write-up draft-reschke-webdav-post-05 Mike Douglass