[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: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-10-20 15:20:20 CEST

Greg Hudson <ghudson@MIT.EDU> wrote on 10/19/2004 07:32:26 PM:

> (Just in case anyone's lost track, I'm not opposed to implement lock
> timeouts at all; we need them for good DAV support. I'm opposed to
> making them visible via the command-line client, the libsvn_client or
> libsvn_ra APIs, or the ra_svn protocol.)

I am sure you all will make the right decisions as to whether lock
timeouts will exist anywhere other than DAV, I would just like to chime in
that I do not see any value in having this feature, especially if it
overly complicates things. If you have to implement the feature anyway
for DAV, and it wouldn't be hard to support it everywhere else too, well,
like I said, I am sure you will make the right decision.

I have worked with several locking version control systems, and I have
never encountered one that had this feature, nor can I imagine why it
would be desired. The argument that it is because people go on vacation
and forget to check stuff back in is totally bogus as there obviously has
to be a system in place to break the locks anyway. Not to mention that
they may still have legitimate changes that should be committed.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 20 15:20:51 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.