- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 17 Feb 2005 18:18:25 +0100
- 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 UTC