UPDATE method and forking

Hi,

The UPDATE method can be used to set the checked-in version of a
version controlled resource to a version which has descendants.
At that point a check-out may fork, resulting in the checked-in
version to have more than one descendant.

This way a tree can be built. If one wants to grow the different
branches of such a tree, the UPDATE method should be used to set
the checked-in version of the version controlled resource
appropriately. This, however, changes global state, which could
lead to races.

The complete operation the client would do is the following sequence:
- Retrieve the current checked-in version of the version controlled resource.
- Set it to the most recent version in a "branch".
- Perform a check-out or anything else that can be done on a version
  controlled resource.
- Set the checked-in version back to what it was.

For this to work in a multi-user environment, either the sequence
should be executed atomically and in isolation, or methods such as
check-out should be allowed to operate on versions as well.

Regards,

Werner.
-- 
Werner Donné  --  Re BVBA
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803	e-mail: werner.donne@re.be

Received on Wednesday, 15 March 2006 09:29:13 UTC