W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2005

[Bug 93] Write Locks and Collections vs MOVE

From: <bugzilla@soe.ucsc.edu>
Date: Wed, 30 Nov 2005 11:28:42 -0800
Message-Id: <200511301928.jAUJSgIB016360@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org


lisa@osafoundation.org changed:

           What    |Removed                     |Added
         AssignedTo|joe-bugzilla@cursive.net    |lisa@osafoundation.org

------- Additional Comments From lisa@osafoundation.org  2005-11-30 11:28 -------
We agreed that the BIND model, where the resource that a collection's member URL
points to is part of the collection's state, is a reasonable model from which to
derive this list.  That implies that even when MOVE/COPY overwrites a
pre-existing member, the lock token of the locked parent collection is still

This has the side benefits of:
 - consistent with existing implementations (greenbytes) which do require lock
in these two cases
 - simpler handling where server always requires the lock token if the
destination parent is locked 

------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Wednesday, 30 November 2005 19:28:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:34 UTC