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

RE: Re: [Issue 533] New - implement reserved checkouts

From: Bill Tutt <rassilon_at_lyra.org>
Date: 2002-08-02 21:16:06 CEST

> From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
> "Bill Tutt" <rassilon@lyra.org> writes:
> > > Maybe I'm confused about terminology? I thought:
> > >
> > > - "advisory lock": a lock that can be overridden or stolen.
> > >
> >
> > When I say advisory lock I mean: A shareable write lock.
> >
> > Multiple people can hold one of these, and anyone of those holders
> > commit changes.
> >
> > Firm lock: Exclusive write lock.
> >
> > Which does mean that only the locker, or an admin can undo the lock.
> Okay, thanks.
> What about stealable firm (i.e., exclusive) locks? Some systems have
> those. Are they just a bad idea?

Concepts first this time:
Give-able exclusive locks: The person (or admin) that owns the exclusive
lock can transactionally give the lock to someone else.

Hrm. Give-able maybe, otherwise we're talking about making an ACL system
even more complicated because you'd want to be able to restrict who can
steal your firm locks. I'm not so enthused with that kind of an idea.
Anything that might complicate ACL matters I'm not especially found of.
Security is annoying, and anything that complicates an already annoying
area should have enough upside to justify the expense. To me, lock
stealing doesn't seem like it meets that bar.

I think Give-able locks are kind of silly btw, just using it as an
example of an alternative simpler idea.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 2 21:16:39 2002

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.