[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Pressing need for exclusive locking

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-09-03 20:39:15 CEST

"Ronald Cannes" <roncannes@hotmail.com> writes:

> 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.

Please, not this debate... again. People have argued for years about
whether 'advisory' locks vs. 'forced' locks are better or necessary.
Some people believe what you say above, that locks be absolutely
unbreakable. Others believe that locks are just communication tools,
and so an advisory lock is just as useful -- if someone forcibly
breaks it, then you have a social/communications problem in your
company, not a software problem.

But rather than debate this -- look at the locking-plan.txt. It's
modeled after the DAV lock specification, which allows both kinds of
locks.

---------------------------------------------------------------------
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:41:08 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.