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

"Clemm, Geoff" <[email protected]>
Newsgroups gmane.ietf.deltav
Message-ID <3906C56A7BD1F54593344C05BD1374B1075FD3E8@SUS-MA1IT01>
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.

Cheers,
Geoff
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.