In the event of a multiple commit path, ie. email-to-twiki, soft-locks and clusters or even pod-to-twiki, there should be a well defined commit cycle/path.

This should be based on some basic rules of behaviour:

• no save shall be committed without a hard-lock-and-comfirm path
• a hard-lock-and-comfirm path shall last no more than XX mintues - XX can be defined
• no save shall be committed in the event of a conflicted-merged

-- NicholasLee - 03 Apr 2001

I think that using hard locks (I assume you mean pessimistic locking, i.e. the current scheme) won't necessarily work when there are many commit paths - some form of optimistic concurrency control, with merge a la CVS, seems like a better option.

-- RichardDonkin - 18 Aug 2001