- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 25 Jul 2002 20:02:25 +0200
- To: "Clemm, Geoff" <gclemm@rational.com>, <w3c-dist-auth@w3c.org>
> From: w3c-dist-auth-request@w3.org > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Clemm, Geoff > Sent: Thursday, July 25, 2002 7:53 PM > To: w3c-dist-auth@w3c.org > Subject: RE: New RFC2518bis draft, COPY / MOVE of live properities > > > > Yes, good point Jason, these constraints should only > apply to MOVE, and definitely not to COPY. > > For COPY, I would like us to use the rfc-3253 semantics, > i.e. that a COPY is semantically equivalent to a GET/PROPFIND > followed by a PUT/PROPPATCH, where the PROPFIND/PROPPATCH > is for all properties that can be PROPPATCH'ed at the destination. This won't work (in all cases). The resource may have multiple representations (depending on request headers), but a simple sequence of GET/PROPFIND-PUT/PROPPATCH will only copy one of the representations.
Received on Thursday, 25 July 2002 14:02:58 UTC