Mark Phippard <markp...@gmail.com> writes: > On Mon, Jun 25, 2012 at 12:16 PM, Philip Martin > <philip.mar...@wandisco.com> wrote: > >> I would probably giving the user a mechanism to ask for exclusive locking >> if the application does not request it.
Oops! I meant to write "I would avoid giving ..." We cannot know whether $APP would work with exclusive locking so unless the application asks for exclusive locking it gets shared locking. The user would also be able to force applications to use shared locking. > I think of apps like TortoiseSVN which have a background process > monitoring working copies to maintain a status cache. These apps > could probably be updated to queue up these checks when they get a > database lock, but in the past they expected to be able to read the WC > even if the user was using the command line at the same time. Such apps should already cope with status failing because a work-queue item is present. The bigger problem might be that with exclusive locking the error is now delayed by Subversion's SQLite timeout. -- Cerified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
