W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2005

Re: draft-reschke-http-addmember-00

From: Jamie Lokier <jamie@shareable.org>
Date: Tue, 22 Feb 2005 20:42:26 +0000
To: Julian Reschke <julian.reschke@gmx.de>
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>
Message-ID: <20050222204226.GF22555@mail.shareable.org>

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.

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! :)

-- Jamie
Received on Tuesday, 22 February 2005 20:42:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:49:39 GMT