- From: Scott Lawrence <scott@skrb.org>
- Date: Tue, 22 Feb 2005 13:36:34 -0500
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Jamie Lokier <jamie@shareable.org>, Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>, WebDAV <w3c-dist-auth@w3.org>, CalDAV DevList <ietf-caldav@osafoundation.org>, HTTP Working Group <ietf-http-wg@w3.org>
On Tue, 2005-02-22 at 17:36 +0100, Julian Reschke wrote: > > So what do I do if a have a resource that accepts HTML form posts, > SOAP > requests and ADDMEMBER-like semantics on the same URL? Either: - Implement it very very carefully. or - Change your server organization so that they use different URLs. > > The only technical reason why a new method would be required in HTTP > > is if the message semantics were different. For example, POST is > > Of course. That's why they are defined to be different from POST. But that's just the point - from the perspective of HTTP, the proposed ADDMEMBER is not fundamentally different from POST.
Received on Tuesday, 22 February 2005 18:36:36 UTC