[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 19:13:07 CEST

On Oct 19, 2004, at 10:32 AM, Greg Hudson wrote:

> On Tue, 2004-10-19 at 11:06, Ben Collins-Sussman wrote:
>> I don't understand: what's wrong with supporting lock timeouts as a
>> 'core' locking feature in the libsvn_repos (or fs) libraries?
> When there's a feature you don't really want for yourself, but which
> you
> have to support for the user of module X, it's good to look for a way
> to
> implement it wholly within module X, so that you don't pollute your
> core
> with stuff only module X cares about.
> Unfortunately, in this case I don't think there's any sane way to do
> that. A well-behaved Apache module does not spawn off a timer process,
> in my world. So we pollute our core a little bit. No big deal.

You can't envision a scenario of a team using svnserve, using locks,
and appreciating a lock-expiration feature?

Sure, the idea of lock-expiration was originally motivated by the DAV
spec and MS Word DAV clients, but that doesn't mean it's automatically
some crazy HTTP-specific feature being ickily shoehorned into
Subversion. It seems like a useful feature to me, even if mod_dav_svn
didn't exist.

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