Re: Atomicity of locks and needs-lock

Edward Harvey wrote:
>>> 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.

Ahh, but the question then becomes - how is it helpful when a file shows
as unlocked in my local cache and does not say that it needs a lock?

-- 
Michael Sinz                     Technology and Engineering Director/Consultant
"Starting Startups"                                mailto:michael.sinz@sinz.org
My place on the web                            http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org