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

Re: [ACL] principal-collection-set

From: Greg Stein <gstein@lyra.org>
Date: Wed, 10 Oct 2001 10:21:58 -0700
To: "DeltaV (E-mail)" <ietf-dav-versioning@w3.org>, ACL@webdav.org
Message-ID: <20011010102158.C4216@lyra.org>
On Wed, Oct 10, 2001 at 12:54:05PM -0400, Clemm, Geoff wrote:
> 1) Keep DeltaV with OPTIONS, and make ACL use OPTIONS for consistency
> 2) Change DeltaV to use properties, and have ACL use properties
> 3) Have DeltaV and ACL use different ways to obtain xxx-collection-set
> The main situation I *really* want to avoid is:
> 4) Change DeltaV to use properties, and have ACL end up using OPTIONS
>    or some other non-property mechanism inconsistent with DeltaV.
> So for those folks that care about this (probably not many :-),
> which choice do you prefer?

#1 big time. This high level information belongs in OPTIONS, queried once
when you first contact the server, to determine what it can support. This
happens before you know that a PROPFIND can be issued.

IMO, it's always been bogus to have protocol/implementation info as a
property. The DAV:lockdiscovery has always given me a twitch.


Greg Stein, http://www.lyra.org/
Received on Wednesday, 10 October 2001 13:17:17 UTC

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