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

[Bug 93] New: Write Locks and Collections vs MOVE

From: <bugzilla@soe.ucsc.edu>
Date: Tue, 11 Oct 2005 23:23:14 -0700
Message-Id: <200510120623.j9C6NE2t004245@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

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

           Summary: Write Locks and Collections vs MOVE
           Product: WebDAV-RFC2518-bis
           Version: -07
          Platform: Other
               URL: http://http://greenbytes.de/tech/webdav/draft-ietf-
                    webdav-rfc2518bis-07.html#rfc.section.7.7
        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


"This means that if a collection is locked (depth 0 or infinity), its lock-token
is required in all these cases:

    * DELETE a collection's direct internal member
    * MOVE a member out of the collection
    * MOVE a member into the collection, unless it overwrites a pre- existing member
    * MOVE to rename it within a collection,
    * COPY a member into a collection, unless it overwrites a pre- existing member
    * PUT or MKCOL request which would create a new member."
    
I disagree with the third one: even if this operation doesn't change the set of
internal member *names*, it definitively changes the set of URI mappings.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Wednesday, 12 October 2005 06:23:17 GMT

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