W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2005

Re: draft-reschke-http-addmember-00

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Mon, 21 Feb 2005 21:24:50 -0700
To: Jamie Lokier <jamie@shareable.org>
Cc: CalDAV DevList <ietf-caldav@osafoundation.org>, HTTP Working Group <ietf-http-wg@w3.org>, WebDAV <w3c-dist-auth@w3.org>
Message-ID: <OF37A764C1.8369E90C-ON85256FAF.007C29A8-87256FB0.0018408A@us.ibm.com>
Jamie Lokier <jamie@shareable.org> wrote on 02/21/2005 02:32:47 PM:
> Geoffrey M Clemm wrote:
> >    But even if a clueless implementation will try to parse the
> >    body of an unknown method like ADDMEMBER, I assume it is very
> >    unlikely that it would say that it supports the ADDMEMBER
> >    method on that resource, so that at least would give the client
> >    a way of avoiding the problem (i.e., by first asking the resource
> >    if it supports the ADDMEMBER function, before attempting it).
> 
> I think that's a reasonable assumption.
> 
> But you should always try to avoid accessing unknown resources, even
> to query their capabilities:  There are implementations where sending
> OPTIONS to them will be interpreted as a POST or stateful GET :)

I'm not sure what you mean by "avoid accessing unknown resources".
The only way a client "knows" about a resource is by doing some discovery
method on it such as OPTIONS.

Cheers,
Geoff
Received on Tuesday, 22 February 2005 04:25:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:07 GMT