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