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

RE: [ACL] principal-collection-set

From: Clemm, Geoff <gclemm@rational.com>
Date: Wed, 10 Oct 2001 13:07:04 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B103F8AC73@SUS-MA1IT01>
To: "DeltaV (E-mail)" <ietf-dav-versioning@w3.org>, ACL@webdav.org
Just to make sure we're on the same page, the interaction between
the client and a server will not be to ask each resource "where is
your xxx-collection-set", but rather to ask the first encountered
resource in a session "where are the xxx-collection-set values on
your server", and then use those values for the rest of the session.

This means that you would not be combining requests for xxx-collection-set
information with the other property information, but rather will be
asking for xxx-collection-set information around the same time you
are asking for OPTIONS information (i.e. what options are supported
by your server), which is why the xxx-collection-set information is
currently marshalled via OPTIONS, since *that* allows you to get all
this "configuration" information in one request.

Cheers,
Geoff  

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
> 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?

Obviously, it MUST be consistent across deltaV, ACL and future WebDAV
versions.

I honestly think that 2) is the best solution. For instance, it allows a
client to collect all it needs to know about a resource with one request.
Received on Wednesday, 10 October 2001 13:07:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:42 GMT