markp...@tigris.org writes: > http://subversion.tigris.org/issues/show_bug.cgi?id=4176
> I think we need to find a way to include this patch. I would suggest > a new runtime configuration option or an environment variable. > Something like "Allow concurrent client access". There are problems with the patch. One is that it is incompatible with the legacy access baton API, so an application using that API will need to have exclusive locking disabled. Another problem is the current implementaion results long-lived SQLite handles so programs using the newer API run into problems if with multiple/long-lived contexts. I think the solution is to default to non-exclusive locking and to allow an application to ask for exclusive locking. Then the command line client can be patched to ask for exclusive locking. And we provide a config option that allows the user to prevent the command line client for asking for exclusive locking so that anyone who relies on the existing 1.7 behaviour can still get it. Somebody would have to test other applications, like TortoiseSVN, to determine whether it is sensible for those applications to ask for exclusive locking. -- Philip
