[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-20 22:50:19 CEST

On Oct 20, 2004, at 3:39 PM, Garrett Rooney wrote:

> Ben Collins-Sussman wrote:
>
>> So I suppose mod_dav_svn can have another private db table (like the
>> activities.db) which can store lock-expiration times. Whenever a
>> client mentions a lock, mod_dav_svn can compare the lock-expiration
>> time (if it exists) with the lock's creation timestamp, and
>> "auto-release" the lock.
>
> That doesn't work so well for repositories that can be accessed by
> more than one RA layer. Someone takes out a 5 minute lock over
> mod_dav_svn, then nobody ever uses the http:// interface again, the
> lock stays there forever, or at least until someone breaks it
> manually. That doesn't seem right...
>

Hm, I suppose you're right. Maybe this means that lock expiration
needs to be a 'core' feature in libsvn_repos, common to all RA
accesses. But we still don't have to expose that feature on the client
side.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 20 22:50:51 2004

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