[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Adding a no-op LOCK to mod_dav_svn

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-01-04 00:58:59 CET

Greg Hudson <ghudson@MIT.EDU> writes:

> The tragedy is not that the clients don't have locking, but that we're
> lying to them. If some clients are overly paranoid (do they actually
> get anything out of obtaining a lock?)

Yes. They get a guarantee that they're not accidentally overwriting
somebody's changes, and a guarantee that nobody will overwrite their
own changes via some race condition.

But remember, these paranoid dav clients are using LOCK because
they're not living in a versioned world. They fear that data could be
permanently lost by accidental stomping. The truth is, there *is*
versioning going on, so the danger isn't really so severe.

So yes, we'd be lying, but with very little real impact. Just an
ethical problem in my mind. :-)

I guess it comes down to the question: it the little white lie worth
it, if it means that all OSes can now mount repositories as
read/write? It's a tradeoff to consider.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 4 01:02:32 2003

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.