Re: Pressing need for exclusive locking

>How about just making an advisory lock? which can be broken. This solves
>the timing problems, and lets people move on when there are dangling lokcs.

First of all, I don't really see any "timing problems". It may not be
straightforward to implement, but not horribly difficult either. And from
the user perspective, it solves a lot of problems.

Second, beeing able to hijack a lock doesn't sound right to me. When you
lease a resource, you should be confident that all other are only reading
it. For some types of files, beeing able to lock it completely is crucial!
It is so crucial that I know several organizations run SourceSafe along with
CVS/SVN simply because of this need.

The lease model appears to solve both the locking and the "forgetting user"
problem.

_________________________________________________________________
Last ned nye MSN Messenger 6.0 gratis http://www.msn.no/computing/messenger
- Den korteste veien mellom deg og dine venner

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 3 20:33:48 2003