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

WebDAV locks (was: [Issue 533] New - implement reserved checkouts)

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-08-06 22:16:02 CEST

On Tue, Aug 06, 2002 at 10:45:52AM +0200, brane@xbc.nu wrote:
> If nothing else, it'll allow the integration of subversion with all those
> DAV-enabled clients out ther (MS Office, MSVC.NET, etc. etc.), which IMHO is a
> compelling enough reason to eventually add locks.

Actually, I've been thinking of faking WebDAV locks, rather than truly
locking the resources. When somebody takes out a lock, we can construct a
transaction and return its name in the lock token. When a PUT comes in with
a lock token, then we extract the token, look up the txn, and store the
file. When the UNLOCK arrives, we commit the txn.

Actually, any change that arrives with a lock token can be redirected to the
SVN txn. And they can even use the "public" URL (since we discriminate based
on the lock token presence), rather than needing to switch over to working
resources (although we can try to redirect clients there by using a
Content-Location header when they do the LOCK). However, if (say) a GET or a
PROPFIND arrives without a lock token, then the user could end up getting a
newly-committed copy rather than the one that they originally fetched.

Of course, the mis-fetch problem also implies that the user's changes will
get (eventually) punted due to a conflict.


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 6 22:12:54 2002

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.