- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sat, 09 Jul 2005 09:18:50 +0200
- To: Lisa Dusseault <lisa@osafoundation.org>
- CC: Webdav WG <w3c-dist-auth@w3c.org>
Lisa Dusseault wrote: > > > Speaking of RFC2518bis, do we have any support for this option in any > WebDAV implementations? I don't recall it being tested in past interops... > > " A resource MAY be a collection but not be WebDAV compliant. That is, > the resource may comply with all the rules set out in this > specification regarding how a collection is to behave without > necessarily supporting all methods that a WebDAV compliant resource > is required to support. In such a case the resource may return the > DAV:resourcetype property with the value DAV:collection but MUST NOT > return a DAV header containing the value "1" on an OPTIONS response." > > If this option isn't implemented or isn't interoperable, let's cut it. As far as I can tell, there's no reason to cut it. It doesn't make the protocol harder to implement, and it may be of value for some servers that choose to implement a subset of WebDAV only (GroupDAV comes to mind). Best regards, Julian
Received on Saturday, 9 July 2005 07:19:10 UTC