- From: Tim Ellison <tim@peir.com>
- Date: Fri, 22 Jun 2001 21:17:51 +0100
- To: "Ietf-Dav-Versioning" <ietf-dav-versioning@w3.org>
> I think we agree to disagree on the complexity issues of > extending DAV:resourcetype as compared to DAV:supported-live- > property-set. Ok. > DAV:supported-live-property-set will by definition be extended > by every future extension to the DAV protocol family. That means > it will automatically have new members with every extension. Agreed. > These new members will change the way how clients interpret > the value of DAV:supported-live-property-set, e.g. its semantics. I disagree. The property still means the set of supported live properties no matter what the size of the set. > > How much more difficult is it to look for multiple values than single > > values? > > Real world example: my client has to detect and work with lock-null > resources. [Snipped problems with IIS, mod_dav and HTTP servers in general.] > Does my client have to work with those servers? It sure does! > > Would I be glad for a resource type lock-null? Take a wild guess. That won't fix the server implementations. Tim
Received on Friday, 22 June 2001 16:17:53 UTC