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

Re: Locking functional spec: timeouts

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-10-18 23:36:10 CEST

On Oct 15, 2004, at 11:54 AM, Greg Hudson wrote:

> On Fri, 2004-10-15 at 01:08, Justin Erenkrantz wrote:
>> Yet, this is going to introduce a whole set of goofiness: locks may
>> not
>> necessarily have to be 'unlocked' - they can just expire. Ideally,
>> we'd go
>> for a lazy expiration model. And, lots of other things need to be
>> thought
>> about timeouts as well from a user perspective.
> I'm not sure if we have to modify the UI spec at all. The functional
> spec just needs an optional timeout field associated with a lock. Only
> DAV locks would ever use it. An svn working copy can assume that its
> own locks don't time out (since it wouldn't have requested them with a
> timeout), and other people's locks timing out is the same as other
> people giving up their locks explicitly.
> (When accessing the lock table, we would ignore and/or clean up locks
> with a timeout in the past, of course.)

I agree. This is relatively simple to implement. The svn client
already needs to be ready to deal with 'defunct' lock tokens. During
an update, a server may tell a client, "sorry, your token is dead,
somebody else released it." Or, it may say, "sorry, your token is
dead, it has expired." No big deal.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 18 23:37:44 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.