[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: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-01-04 18:22:38 CET

On Sat, 2003-01-04 at 07:17, Julian Reschke wrote:
> This sounds like you're suggesting to allow multiple clients to WebDAV-LOCK
> the same resource at the same time, obtaining the same lock token.

I didn't say the lock token would only contain the crev or
node-revision-id; it could also contain a uniquifier.

Unfortunately, I can't come up with a totally correct abstract
justification for a stateless lock mechanism. I could say that when the
second client asks for a lock (or even asks for "lock discovery" per RFC
2518 section 6.6), the first client's lock is abstractly discarded. But
that's not really true; the first client's lock will still be honored as
long as the resource has not been changed.

(We can, however, hack around the problem of determining which
lock-holder modified a resource, by storing the lock token in a property
of auto-versioned commits.)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 4 18:23:29 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.