W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2005

Re: [Ietf-caldav] [Fwd: draft-reschke-http-addmember-00]

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 17 Feb 2005 18:18:25 +0100
Message-ID: <4214D1E1.9030700@gmx.de>
To: Jamie Lokier <jamie@shareable.org>
CC: "Roy T. Fielding" <fielding@gbiv.com>, Mark Baker <distobj@acm.org>, HTTP Working Group <ietf-http-wg@w3.org>, CalDAV DevList <ietf-caldav@osafoundation.org>, WebDAV <w3c-dist-auth@w3.org>

Jamie Lokier wrote:
> Julian Reschke wrote:
> 
>>>>2) Atom's approach is to use service URIs to which the client can POST, 
>>>>and to discover these service URIs by parting entity (feed) bodies.
>>>
>>>...
>>>
>>>
>>>>2) Is specific to Atom and not applicable to other protocols.
>>>
>>>
>>>ADDMEMBER is no different from POST in this respect:
>>>
>>>You still have to "discover the service URI" to use with ADDMEMBER.
>>
>>No, it would be the container resource itself. For CalDav, the calendar 
>>collection; for Atompub, the feed resource itself.
> 
> 
> Why can't you POST to the container resource?
> 
> That's what POST is for, after all.

Because in general, I will have no idea what the server will do with the 
POST.

Best regards, Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Thursday, 17 February 2005 17:19:01 GMT

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