Re: COPY method and activity feature

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

Some of the rationale for not doing this was:

- We cannot do this everywhere where it would matter, since, for example,=20
the body of PUT (which also can cause automatic check-outs) is not=20
available for extensions.
- A versioning aware client can explicitly CHECKOUT the VCR to achieve=20
this effect (and a versioning-unaware client would not know to set the=20
activity in the body of the COPY).
- A client will commonly just set the workspace current activity, and not=20
be overriding this in individual checkouts anyway (this is what is always=20
done to set things up for a versioning-unaware client).

Cheers,
Geoff



Werner wrote on 09/14/2006 06:11:00 AM:
> When the activity feature is supported the CHECKOUT method
> may have an activity-set body. Shouldn't this also be the
> case for the COPY method when the auto-version feature is
> also supported? The copy of a collection can cause several
> automatic check-outs.
>=20
> Regards,
>=20
> Werner.
> --=20
> Werner Donn=E9  --  Re
> Engelbeekstraat 8
> B-3300 Tienen
> tel: (+32) 486 425803   e-mail: [email protected]
>=20

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


<br><tt><font size=3D2>Some of the rationale for not doing this was:</font>=
</tt>
<br>
<br><tt><font size=3D2>- We cannot do this everywhere where it would matter,
since, for example, the body of PUT (which also can cause automatic check-o=
uts)
is not available for extensions.</font></tt>
<br><tt><font size=3D2>- A versioning aware client can explicitly CHECKOUT
the VCR to achieve this effect (and a versioning-unaware client would not
know to set the activity in the body of the COPY).</font></tt>
<br><tt><font size=3D2>- A client will commonly just set the workspace curr=
ent
activity, and not be overriding this in individual checkouts anyway (this
is what is always done to set things up for a versioning-unaware client).</=
font></tt>
<br>
<br><tt><font size=3D2>Cheers,</font></tt>
<br><tt><font size=3D2>Geoff</font></tt>
<br>
<br>
<br>
<br><tt><font size=3D2>Werner wrote on 09/14/2006 06:11:00 AM:<br>
&gt; When the activity feature is supported the CHECKOUT method<br>
&gt; may have an activity-set body. Shouldn't this also be the<br>
&gt; case for the COPY method when the auto-version feature is<br>
&gt; also supported? The copy of a collection can cause several<br>
&gt; automatic check-outs.<br>
&gt; <br>
&gt; Regards,<br>
&gt; <br>
&gt; Werner.<br>
&gt; -- <br>
&gt; Werner Donn=E9 &nbsp;-- &nbsp;Re<br>
&gt; Engelbeekstraat 8<br>
&gt; B-3300 Tienen<br>
&gt; tel: (+32) 486 425803 &nbsp; e-mail: [email protected]<br>
&gt; <br>
</font></tt>
--=_alternative 0040A865852571E9_=--