[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:36:27 CEST

Okay, I give in. :-)

It's really a question of "what's uglier?"

   * putting a lock-expiration feature into core libraries.
   * making only mod_dav_svn implement lock-expiration.

I feel that code-wise, if you're going to implement a feature, you
should implement it everywhere: libsvn_repos, commandline client, and
so on. I hate the ugliness of features specific to RA layers.

But if this a feature that nobody wants or cares about, and serves only
to pollute/complicate our UI, then heck, I guess that's at least as
ugly a situation.

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.

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:36:54 2004

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