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

[Bug 193] New: LOCK_ISSUES_WRITE_LOCK

From: <bugzilla@soe.ucsc.edu>
Date: Mon, 21 Nov 2005 09:27:48 -0800
Message-Id: <200511211727.jALHRmOH004643@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

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

           Summary: LOCK_ISSUES_WRITE_LOCK
           Product: WebDAV-RFC2518-bis
           Version: -08
          Platform: Other
               URL: http://lists.w3.org/Archives/Public/w3c-dist-
                    auth/1999AprJun/0246.html
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: 07.  Write Lock
        AssignedTo: joe-bugzilla@cursive.net
        ReportedBy: julian.reschke@greenbytes.de
         QAContact: w3c-dist-auth@w3.org


Reported by Jason Crawford in
<http://lists.w3.org/Archives/Public/w3c-dist-auth/1999AprJun/0246.html>:

Section 7.1 Write lock. 
I believe this definition of a write lock is not right... or not complete...
judging from what I read elsewhere. I believe one can do these operations
without a write lock... as long as someone else doesn't have a write lock on the
resources effected. I also believe it doesn't prevent LOCK requests in the case
of shared locks.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Monday, 21 November 2005 17:27:53 GMT

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