AW: Conflict detection in DeltaV using ServerSide Workspace

So here is my next approach to detect conflicts on server-side;-)

Preconditions:=20
- the server allows checkout-fork=20
- checkin-fork will always be forbidden. (See chapter 11.7.2 in in =
Dusseault=B4s book)

The client creates a private activity and does a =93checkout=94 of his =
files to the activity. Furthermore the client adds a =
=93apply-to-version=94 element inside the checkout request. This turns =
the VCR in a =93Working Resource=94 so that every client has its own =
working copy.

Now we come to the conflict detection:

When the client =93checkin=94 the activity, all his private working =
resources will be automatically checked-in by the server. When someone =
else already changed and checked in a VCR that is in our activity (a =
conflict) the server will see, that the predecessor-set to what our =
working resources points to, already has a successor. In this situation =
the server normally has to do a fork. Checkin-fork is forbidden by the =
server so the server return an errors message.

Is this a possible approach?

Thanks for your answers :-)

  Martin=20