W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2002

RE: Marshalling DAV:xxx-collection-set as a live property, and not an OPTIONS request.

From: Julian Reschke <julian.reschke@greenbytes.de>
Date: Sun, 7 Jul 2002 16:21:30 +0200
To: "Clemm, Geoff" <gclemm@rational.com>, "DeltaV \(E-mail\)" <ietf-dav-versioning@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCAEGKEOAA.julian.reschke@greenbytes.de>

> From: ietf-dav-versioning-request@w3.org
> [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Clemm, Geoff
> Sent: Sunday, July 07, 2002 2:59 PM
> To: DeltaV (E-mail)
> Subject: Marshalling DAV:xxx-collection-set as a live property, and not
> an OPTIONS request.
> 
> 
> 
> Since I was not able to convince the ACL working group to marshall
> this kind of information as an OPTIONS request, we should probably
> consider changing the versioning protocol to also marshall this
> kind of information (i.e. DAV:workspace-collection-set,
> DAV:activity-collection-set, and DAV:version-history-collection-set)
> as live properties, and not as OPTIONS requests.
> 
> So I'd like to poll the mailing list (especially DeltaV client and/or
> server implementors:
> 
> Do you prefer to:
> (a) leave xxx-collection-set as it is (marshalled only as OPTIONS)
> (b) support marshalling both as OPTIONS and as live properties
> (c) marshal only as live properties and deprecate the OPTIONS marshalling
> 
> I vote for (c), as it simplifies the spec, and makes it consistent
> with the ACL protocol.

Same for me (c).
Received on Sunday, 7 July 2002 10:22:13 GMT

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