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

[Bug 24] lost-update vs collections

From: <bugzilla@soe.ucsc.edu>
Date: Wed, 23 Nov 2005 16:51:04 -0800
Message-Id: <200511240051.jAO0p4eH008770@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=24

lisa@osafoundation.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From lisa@osafoundation.org  2005-11-23 16:51 -------
Good point -- it's getting the lock that clients want a high likelihood of
achieving, so:

When trying to lock a collection upon 
   creation, clients may attempt to increase the likelihood of getting the lock by 
      pipelining the MKCOL and LOCK requests together (but because this 
      doesn't convert two separate operations into one atomic operation 
      there's no guarantee this will work).  



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Received on Thursday, 24 November 2005 00:51:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:11 GMT