Description Jean-Michel Lemieux 2001-10-10 21:34:53 EDT

With the current VCM API, a repository adapter can either be pessimistic or 
optimistic.
	If it is pessimistic, all check-outs are "reserved", i.e. no other user 
is allowed to check
	out the same resource. If it is optimistic, no check-out is "reserved".
	In other VCM systems (e.g. CC and CVS), you can decide on a resource-by-
resource basis
	if a check-out should be "reserved" or not.
	Usually, a check-out is not "reserved" if a merge is not difficult, 
e.g. if there are merge tools.
	If there are no merge tools, and a merge by hand is not trivial, the 
check-out should be a
	"reserved" check-out.

NOTES:

BB (3/1/2001 9:36:23 AM)
	Proposed change to the VCM API: checkout() takes an additional boolean 
parameter
	"reserved" and the corresponding activity event is changed accordingly. 
Does not seem relevant for
	CVS. Moving to Active_MarkH for comment.

SK (4/11/2001 6:10:17 PM)
	This will be solved via use of ICCActivity to do checkout and unlock.

SK (4/25/2001 3:49:50 PM)
	Moving back to active, as this work is only a release candidate.

KM (4/25/01 4:42:08 PM)
	From note from Mark H:
		I am not exposed to the whole development
		community, so I am not aware of what people are complaining 
about/asking
		for.  It is needed if we want to support serial development.

		Estimated development time is 1 week by Steve, so I would think 
that puts
		it in the future bucket by necessity.

Jean-Michel (11/06/2001 9:37:22 AM)
	Our current internal VCM API does not support a pessimistic model.