[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: Josh Pieper <jjp_at_pobox.com>
Date: 2004-05-20 22:15:14 CEST

Branko ??ibej wrote:
> Josh Pieper wrote:
> >Speaking of shared locking, is there some specific semantics for
> >shared locking that you're referring too? How would that work, a
> >client requests a lock and states that at most N other clients may
> >hold the lock at the same time? I was unable to find anything
> >resembling that in the WebDAV spec.
> >
> >
> The DAV spec speaks of shared (read and write) locks, but doesn't
> specify how they behave. Therefore we can do anything that's reasonable.
> 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.

If every PUT caused a commit without using shared transactions, the
same result would occur, correct? All clients who hold the shared
lock would see the results as soon as a PUT is issued. It would just
have the side effect of allowing clients who don't have the shared
lock to see the results of each PUT as well.


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