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

[Bug 195] New: LOCK_ISSUES_WRITE_LOCKS_AND_COPYMOVE

From: <bugzilla@soe.ucsc.edu>
Date: Mon, 21 Nov 2005 09:30:02 -0800
Message-Id: <200511211730.jALHU2un004676@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

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

           Summary: LOCK_ISSUES_WRITE_LOCKS_AND_COPYMOVE
           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>:

7.7 Write Locks and COPY/MOVE 
It says that a lock doesn't move with a moved resource. Of course if the lock is
on the resource, not the URI, it should move with the resource. But then we have
the caveat that we are also protecting the LOCK'd URI. I think the rule should
be that if we submit the locktoken with the MOVE request, we are allowed to have
the LOCK move with the resource and the lock will now protect a different URI.
Also, ALL locks in the subtree must be submitted or the MOVE must fail because
otherwise it would break our URI protection rule.



------- 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:30:06 GMT

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