- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 22 Feb 2005 20:23:56 +0100
- To: Jamie Lokier <jamie@shareable.org>
- CC: 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>
Jamie Lokier wrote: > Julian Reschke wrote: > >>I'm not sure what your point is. Of course if a server mishaves that >>way, a client accessing it may cause problems. But that's the problem of >>the server, and I don't think there's anything we can do about that when >>discussing HTTP based protocols. >> >>What am I missing? > > > You're missing that when you are doing CalDAV* requests, you _know_ the > URL you are accessing is CalDAV compliant already. (* - example). How does a client do *any* kind of server feature discovery if *any* method (including things like OPTIONS) may cause harm because of broken server implementations? > If you don't know that you have big problems. Such as? > So you don't need new methods just to express "intent". > (Maybe for other reasons, but not this one). Best regards, Julian -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Tuesday, 22 February 2005 19:24:33 UTC