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, JulianReceived on Saturday, 9 July 2005 07:19:10 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:09 GMT