--On Monday, April 28, 2003 10:44 AM -0700 Zitan Broth <zitan@mediasculpt.net>
wrote:
> I was looking at
> http://svnbook.red-bean.com/html-chunk/apds02.html#svn-app-d-sect2.3 and
> there they mention that you can use mod_dav_lock (requires Apache 2.1+) to
> handle locking files. Although the SVN specific client can break these
> (with a SVN commit), but that seems to be a viable solution if normal uses
> are using DAV and only admin users access the system via the SVN client.
> Obviously it would be nicer to have consistent LOCK and UNLOCK, but I am
> also pretty happy with the incremental change implementation ;-)
>
> Don't know if that helps, but thought I'd mention it :-)
Yup, mod_dav_lock was meant to integrate with non-SVN-ish clients not SVN
itself. Although I wonder how hard it'd be to have SVN do a LOCK/UNLOCK if it
is against a Class 2 DAV server. That doesn't solve the ra_svn problem, but
it'd solve the slightly more common case where ra_dav clients are used with
plain WebDAV clients.
For a solution that works with ra_svn and ra_dav and external clients, you'd
have to implement the full-blown locking scheme which no one wants to do now.
/me hums "if I only had free time" -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 30 10:08:33 2003