RE: Atomicity of locks and needs-lock

> > In particular, the file should become read-only, and in the gui,
> > change the icon to gray.
>
> Here is where things get difficult - how do you expect this to happen?

What I'm hoping for is for subversion to cache the most recently known
lock status in the entries file. The only reason the info can't be
shown today is because in order to get the information, you have to
contact the repository, and it's not reasonable to contact the
repository every time you do a file listing.

Of course the data in the cache would only be as accurate as the most
recent update, but I think that's understandable and expected. Everyone
accepts the fact that subversion is a pull, not push, mechanism. And
everyone encourages the habit of regular updates (or at least status
checks). To reduce the chance of wasting time by working on something
that has already been outdated.

(Actually, caching the lock information doesn't seem to be unpopular.
How to handle the data is strongly debated.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 30 19:35:53 2006