[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: Justin Erenkrantz <jerenkrantz_at_apache.org>
Date: 2003-01-05 09:48:41 CET

--On Saturday, January 4, 2003 6:44 PM -0800 Greg Stein
<gstein@lyra.org> wrote:

> It will be interesting to see how well [mod_dav_lock] works with
> mod_dav_svn. Also, whether it can detect a "loss of lock" if the
> repository changes through something besides DAV (e.g. local
> access).

It worked in my limited testing with mod_dav_svn (see commit to that
to use the locks if mod_dav_lock is available).

As far as detecting 'loss of lock,' I'm not really sure what we could
do. I wonder if we stored the ETag with the lock and verified the
ETag was identical in the lock precondition tests (where we check if
the lock has expired). Does mod_dav_svn allow easy computation of
the etag? ISTR a mod_dav hook for getting the etag for a resource.

Or, do we have to toss locks when the commit is made? I don't think
we can toss on commit, because a commit could be made via ra_svn and
our code would never get called. It seems we'd have to verify them
when the lock is attempted to be used (or an operation on a locked
resource).

I'm going to try to spend some time working on Issue #773 now that
I've got autoversioning working for me. If people have thoughts or
suggestions to mod_dav_lock, patches are welcomed. =-) -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jan 5 09:49:25 2003

This is an archived mail posted to the Subversion Dev mailing list.