SteveKing <email@example.com> wrote on 04/08/2005 01:58:07 PM:
> I'm currently working on the new features in Subversion 1.2. And as you
> may have already heard, the main feature is locking.
> So I need your ideas on how to implement this. Sure I have own ideas,
> but they just don't feel right.
> Ok, so here goes what we have to do:
> - files can be locked (surprise).
> - Two new context menu entries "lock" and "unlock" will be implemented
> Now comes the problem:
> We can attempt to lock the selected files, but that can fail if e.g.
> another user already has one of those selected files locked. Not a big
> deal really. But now, the user can 'steal' the lock, i.e. just override
> the other users lock.
> So, how should we do this in an UI way?
> - try to lock, throw an error if someone else already has the lock,
> don't allow to override the lock at all.
> - before attempting to lock, ask the user if he want's to override a
> maybe existing lock and then just force the lock no matter what
> - Allow to redo the lock from the progress dialog once a lock has failed
> and this time just steal the lock
> - ???
> Oh, and the same applies to removing a lock:
> you can remove a lock even if you're not the owner of the lock by
> 'breaking' the lock.
> So please, think of how the UI should handle this situation and make
I think it would be a good idea to ask the Subversion devs their opinions.
Or at least maybe email Ben Collins-Sussman to get his opinion.
I tend to lean towards the first option, just error out. Perhaps have a
message that lets them know they might be able to break someone else's
lock by using the unlock option.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Apr 8 20:04:32 2005