> > AFAIK, the subversion folks and tortoisesvn folks seem to
> accept the
> > idea of caching the most recently known lock status, for
> locks that are owned by other users.
>
> Could you please post some links to the mails confirming
> this? I can't seem to find any... :-(
I asked a few times if anybody had objections to the idea of caching the
most recently known remote lock status.
Most of the discussion that ensued was not about whether or not to cache
the info. Most of the discussion turned into *what to do* with the
information if it were cached, and debates about whether or not those
are good behaviors.
In response to the diverse thoughts about how to handle the information,
if cached, I came up with a couple of simple checkboxes. This way, by
default, there is no change of behavior, and no disruption of any
already established workflow. But there is the ability, optionally, to
change the behavior of your own client. To inform and caution yourself
against editing a file if it was most recently known to be locked by
some other user.
As I said, there was very little discussion about caching. Although
there were disagreements on how to handle the info if cached, there were
no objections to the idea of caching, and only a couple of responses
that supported the idea.
Here is what I could find:
First time asking:
http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=48246
Some users list possible problems. Basically, local cached data can be
outdated. Which is true no matter whether the data is remembered by
software or the human brain. So I don't consider this to be an
objection to the idea of caching on disk.
One person felt it would be a good idea:
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=115398
--------- The basic idea, as it stands right now is:
First, store the most recently known remote lock status in the entries
file, so the user doesn't have to store this in his/her brain.
Second, when and if that information is stored in software, I hope to
add some checkboxes in tortoisesvn like this (unchecked by default, to
preserve present behavior) --
Files that are locked by other users,
at the time of the most recent local update:
[X] Use the gray icon
[X] Make the file read-only
[X] It is ok to lock files that don't have the
needs-lock property. Don't warn me.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed May 10 18:12:25 2006