[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-19 17:06:36 CEST

On Oct 18, 2004, at 6:29 PM, Branko Čibej wrote:

> No, it's not. I meant that Subversion /qua/ Subversion shouldn't
> support lock timeouts. But mod_dav_svn (not ra_dav!) obviously has to.

I don't understand: what's wrong with supporting lock timeouts as a
'core' locking feature in the libsvn_repos (or fs) libraries? As
ghudson suggested, the expiration time can be just another field in the
repository's representation of a lock. When some process -- whether it
be svnserve, apache, or ra_local -- tries to use the lock, or runs 'svn
update', or whatever, libsvn_repos code checks that the lock hasn't yet
expired. If it has, then it throws an error and/or tells the client
that the lock is defunct, and then deletes the lock object.

I don't think we need a special daemon hanging around, trying to delete
expired locks. Expired locks can be detected and tossed "lazily", only
when something lists or examines them.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 19 17:08:01 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.