  Re: Bindings, Locks, and MOVE  From: <ccjason@us.ibm.com>
Date: Thu, 16 Sep 1999 13:20:19 -0400 cc: w3c-dist-auth@w3.org
Message-ID: <852567EE.005EA219.00@D51MTA07.pok.ibm.com>    From:
ccjason@us.ibm.com     <jc/> Geoff, please check me if I'm
wrong... but I think kevin is    talking about COPY/MOVE'ing
***TO** the multiply bound resource, not    from.  As currently
written, the COPY/MOVE does a delete on the    destination right
up front... so the binding to a shared object is    lost.  A PUT
to either URI of the resource doesn't break their ability    to
share the resource.     Ooops!  Jason is completely right.
Sorry about the bandwidth wastage.    So I'd like to retract my
earlier posting, and just agree with Kevin    that a COPY that
preserves destination bindings is a useful operation    that is
currently not provided by the protocol.     As a form of
penance, I will propose a solution to this problem:     Add
"DAV:merge" as a new potential value of the Overwrite header
when used with the COPY re