Re: COPY collection to an existing resource

This is a multipart message in MIME format.
--=_alternative 003B2DC5852571A9_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

I agree with Julian that this is what should happen.
This is what section 1.7 is intended to make clear (but apparently wasn't=20
fully successful :-).

Cheers,
Geoff


Julian wrote on 07/12/2006 06:07:23 AM:
>=20
> Werner Donn=E9 schrieb:
> > Hi,
> >=20
> > Say we want to copy a collection to an existing version controlled
> > resource in a repository that puts everything under version control
> > automatically. The version history of the destination should be
> > kept and the resource should be updated.
> >=20
> > What should happen if the source and destination collection have
> > internal members with the same name? Should the internal members
> > in the destination collection also be updated or should the
> > destination collection get new version controlled resources for
> > those?
>=20
> I think they should be updated, although RFC3253 isn't very clear on=20
> that. Check=20
> <http://greenbytes.de/tech/webdav/rfc3253.html#rfc.section.1.7> and=20
> <http://greenbytes.de/tech/webdav/draft-ietf-webdav-rfc2518bis-15.
> html#rfc.section.9.8.4>.
>=20
> Best regards, Julian
>=20

--=_alternative 003B2DC5852571A9_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><tt><font size=3D2>I agree with Julian that this is what should happen.=
</font></tt>
<br><tt><font size=3D2>This is what section 1.7 is intended to make clear
(but apparently wasn't fully successful :-).</font></tt>
<br>
<br><tt><font size=3D2>Cheers,</font></tt>
<br><tt><font size=3D2>Geoff</font></tt>
<br>
<br>
<br><tt><font size=3D2>Julian wrote on 07/12/2006 06:07:23 AM:<br>
&gt; <br>
&gt; Werner Donn=E9 schrieb:<br>
&gt; &gt; Hi,<br>
&gt; &gt; <br>
&gt; &gt; Say we want to copy a collection to an existing version controlle=
d<br>
&gt; &gt; resource in a repository that puts everything under version contr=
ol<br>
&gt; &gt; automatically. The version history of the destination should
be<br>
&gt; &gt; kept and the resource should be updated.<br>
&gt; &gt; <br>
&gt; &gt; What should happen if the source and destination collection have<=
br>
&gt; &gt; internal members with the same name? Should the internal members<=
br>
&gt; &gt; in the destination collection also be updated or should the<br>
&gt; &gt; destination collection get new version controlled resources for<b=
r>
&gt; &gt; those?<br>
&gt; <br>
&gt; I think they should be updated, although RFC3253 isn't very clear
on <br>
&gt; that. Check <br>
&gt; &lt;http://greenbytes.de/tech/webdav/rfc3253.html#rfc.section.1.7&gt;
and <br>
&gt; &lt;http://greenbytes.de/tech/webdav/draft-ietf-webdav-rfc2518bis-15.<=
br>
&gt; html#rfc.section.9.8.4&gt;.<br>
&gt; <br>
&gt; Best regards, Julian<br>
&gt; <br>
</font></tt>
--=_alternative 003B2DC5852571A9_=--