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

Re: Exclusive Locking: design in a nutshell

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-05-20 20:51:28 CEST

Ben Collins-Sussman <sussman@collab.net> wrote on 05/20/2004 02:40:22 PM:

> On Thu, 2004-05-20 at 13:23, Branko Čibej wrote:
> > The DAV spec speaks of shared (read and write) locks, but doesn't
> > specify how they behave. Therefore we can do anything that's
> > IMHO the only thing that's reasonable is for all clients that have a
> > shared lock on the same object to see the same contents. Ergo,
> > transaction-per-lock.
> I really don't like the idea of "lock holders" seeing one thing when
> they GET, and the rest of the world seeing something else. It goes
> against the very principles of Subversion, as Jani pointed out.

What happens in the DAV spec if the user later cancels their LOCK? Do
those previous PUT's get discarded or committed? If the former, then it
seems odd that the DAV server should have previously handed out those now
invalid versions to someone that did a GET.

I like the idea of PUT doing a commit while retaining the LOCK.

Received on Thu May 20 20:52:04 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.