RE: Atomicity of locks and needs-lock

> > I am asking here, if there is any reason against local storing the
> > remote lock information.
>
> Because we can't keep it up to date reliably. It would be a
> faulty cache.

No matter what, all of your local info is only as recent as your most
recent update. The same is true for any change that is committed by
another person. You don't know about it till you check.

At present, if a user checks to see which files are locked, he/she has
to simply remember that info in their brain. Their brain's cache is
only as good as their most recent check. The only difference I'm
suggesting is to use the computer's memory instead of the human's
memory. The computer does a better job.

People are willing to accept that changes are happening in the
repository, and that it's not a push model. People are willing to
accept the behavior of regularly updating themselves.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 29 23:51:19 2006