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

Re: Locking design (was Re: svn commit: r9885 - trunk/notes)

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-05-27 05:59:41 CEST

On Wed, 2004-05-26 at 20:36, C. Michael Pilato wrote:
> While I was kinda anti-directory-lock, I fear that by *not*
> implementing directory locks, we're going to open up a larger can of
> worms (from a performance and elegance standpoint). As soon as
> UserOfLargeBinaryfulRepos realizes he can't lock his massive tree of
> digital video resources, he'll do something worse -- recursively lock
> each resource in that tree.

I imagine this would only happen with any frequency if we made it easy
to get a recursive lock.

But it seems more likely that the need wouldn't arise much at all.
Until Branko said he had an interest in locking release branches (which
I don't understand as of yet), I had seen zero requests for the ability
to lock whole trees of files. Unless you plan to make unmergeable
changes to a whole tree of files (in which case you're going to use lots
of server resources making a big commit anyway, and the locking overhead
will only be commensurate with that cost), why would you want to lock
all of them?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 27 06:01:18 2004

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.