W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2001

Re: Option abuse

From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
Date: Mon, 12 Feb 2001 17:09:26 -0500 (EST)
Message-Id: <200102122209.RAA04013@tantalum.atria.com>
To: ietf-dav-versioning@w3.org

The argument for using PROPFIND to get the information that varies
from resource to resource (as opposed to information that varies
from server to server) is that it allows you to get a consistent
set of information in one Depth PROPFIND request, whereas if you had to
do both PROPFIND and OPTIONS requests, you'd have to first lock
that collection to make sure that things didn't get moved around
between your PROPFIND and your OPTIONS requests, and it is always
unfortunate to have to lock something just for consistent read access.

So other than it being ridiculous and bogus (:-), what harm is there
in making DAV:supported-method-set, DAV:supported-live-property-set,
and DAV:supported-report-set live properties?


   From: Greg Stein <gstein@lyra.org>

   IMO, it is still quite ridiculous to do some discovery through OPTIONS, and
   other discovery through PROPFIND. OPTIONS is defined to be per-resource (if
   you want general server options, the use "*" for the Request-URI).
   Arbitrarily classifying a subset of information as "more useful in a Depth:
   context, so we'll put it into PROPFIND" is just that: arbitrary. In layman's
   terms, that is a synonym for "bogus". :-)

Received on Monday, 12 February 2001 17:10:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:46 UTC