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

[Bug 193] LOCK_ISSUES_WRITE_LOCK

From: <bugzilla@soe.ucsc.edu>
Date: Wed, 21 Dec 2005 11:21:14 -0800
Message-Id: <200512211921.jBLJLE00015324@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

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

elias@cse.ucsc.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From elias@cse.ucsc.edu  2005-12-21 11:21 -------
Issue mostly resolved in -09 draft but for the following...

A shared write lock allows additional shared write locks to be taken out on the
resource. Hence, consensus is to replace:

"A shared write lock prevents the same operations, however it also allows access
by any principal that has a shared write lock on the same resource."

with:

"A shared write lock prevents the same operations (except additional requests
for shared write locks), however it also allows access by any principal that has
a shared write lock on the same resource."

or something substantially similar...



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Wednesday, 21 December 2005 19:21:19 GMT

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