[Ietf-caldav] [Fwd: draft-reschke-http-addmember-00]
bernard.desruisseaux at oracle.com
Mon Feb 21 21:19:23 PST 2005
Ideally we would have a solution that would work for all methods that
may request the creation of a new resource (e.g, LOCK, PUT, COPY, MOVE,
MKCOL, MKWORKSPACE, MKACTIVITY, MKCALENDAR, ...).
Could the solution be as simple as specifying an empty query component
(e.g., "?") in the Request-URI for those methods, and have the methods
return the Location header as part of their response?
would request the server to create a new resource in the collection
/calendar/bernard/ and let the server chose the name of the resource.
Is there already a defined use for the query component for the methods
Cyrus Daboo wrote:
> Hi Julian,
> --On February 17, 2005 2:54:38 PM +0100 Julian Reschke
> <julian.reschke at gmx.de> wrote:
>> 1) CalDav's approach is: use PUT to an arbitrary member URI of the
>> container; then let the server automagically move it somewhere else, and
>> report that in the Location response header
> I want to add that in the CalDAV case this URI naming restriction will
> also apply to COPY and MOVE methods too, not just PUT. So we do need to
> come up with a solution that at least works with those methods too. Of
> course it is possible to emulate COPY and MOVE using PUT (client
> downloads original data, creates it in new location) and DELETE (remove
> old data in the case of MOVE) - but we should really have the proper
> atomic operations for this.
More information about the Ietf-caldav