W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2004

Re: Issue 2.5_language, was: ID: draft-ietf-webdav-bind-05

From: Lisa Dusseault <lisa@osafoundation.org>
Date: Wed, 23 Jun 2004 12:44:27 -0700
Message-Id: <BCB3B512-C54D-11D8-B2D4-000A95B2BB72@osafoundation.org>
Cc: w3c-dist-auth@w3.org, Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
To: Julian Reschke <julian.reschke@gmx.de>

This has a little problem with terminology:

>    If the destination collection of a MOVE request supports the REBIND
>    method (see Section 6), a MOVE of a resource into that collection 
> MAY
>    be implemented as a REBIND request.

The "destination collection" seems here to refer to the collection 
named in the Request-URI, not the collection named in the Destination 
header.  Since destination collection is ambiguous, this could be the 
"target collection", the "collection named in the Request-URI", or "the 
collection named in the Destination header".  Those aren't all the same 
thing obviously.

The rest is a good addition to the spec.

thanks,
Lisa


> Although [RFC2518] allows a MOVE
>    to be a non-atomic operation, when the MOVE operation is implemented
>    as a REBIND, the operation is atomic.  In particular, applying a 
> MOVE
>    to a Request-URI and a Destination URI has the effect of removing a
>    binding to a resource (at the Request-URI), and creating a new
>    binding to that resource (at the Destination URI).
>
>    As an example, suppose that a MOVE is issued to URI-3 for resource R
>    below (which is also mapped to URI-1 and URI-2), with the 
> Destination
>    header set to URI-X.  After successful completion of the MOVE
>    operation, a new binding has been created which creates the URI
>    mapping between URI-X and resource R.  The binding corresponding to
>    the final segment of URI-3 has been removed, which also causes the
>    URI mapping between URI-3 and R to be removed.  If resource R were a
>    collection, old URI-3 based mappings to members of R would have been
>    removed, and new URI-X based mappings to members of R would have 
> been
>    created.  Even when the Request-URI identifies a collection, the 
> MOVE
>    operation involves only removing one binding to that collection and
>    adding another.
>
>    >> Before Request:
>
>     URI-1   URI-2    URI-3
>       |       |        |
>       |       |        |      <---- URI Mappings
>       |       |        |
>    +---------------------+
>    |     Resource R      |
>    +---------------------+
>
>    >> After Request:
>
>     URI-1   URI-2    URI-X
>       |       |        |
>       |       |        |      <---- URI Mappings
>       |       |        |
>    +---------------------+
>    |     Resource R      |
>    +---------------------+
>
>
>
>
> Best regards, Julian
>
> -- 
> <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
>
Received on Wednesday, 23 June 2004 15:45:51 GMT

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