- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 22 Feb 2005 21:49:19 +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: > >>>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? > > > Even when you can trust OPTIONS, that's not going to tell you if it's > a CalDAV resource - only what methods are accepted. I'm not interested whether it's a CalDAV resource. I'm interested in whether it supports ADDMEMBER. > You do feature discovery - in other words, which URL points to a > calendar - in other ways. > > >>>If you don't know that you have big problems. >> >>Such as? > > > Such as trying to treat a non-calendar resource as a calender! :) And the problem resulting from that would be what exactly? A CalDAV calendar (as currently proposed) is just a WebDAV collection with some specific features. Julian -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Tuesday, 22 February 2005 20:49:56 UTC