Re: Communication of CHANGES

Bicking, David (HHoldings, IT) wrote:
>
> And I thought we were discussing the merits of the as yet not
> implemented single cache maintained by Subversion, as opposed to the
> already known to be a problem scenario of multiple caches maintained by
> individual clients. I guess I got my wires crossed.

Someone earlier in the thread tried to separate the discussion of the
display of the cached status info that GUI's do retain from the one
about using locks to imply needs-lock to other people.

>> I can hit buttons in two windows before a command can complete.
>
> So you're saying that you can and WILL click "update" menu items in two
> different GUI's within 1/2 second time? Why would you do that?

My normal working mode is to have about 20 windows open all the time
(some local, some remote) and after starting anything that might take
time to complete in one window I immediately jump to another. Short
attention span, I guess...

> I
> thought the idea was to do less work, not more. I guess I was wrong
> when I said the effort necessary is greater than the desire to do it
> just to break it.

I wouldn't intentionally plan to do the same thing at the same time in 2
different windows, but it happens.

>> And you need to notify other watchers when the contents
>> change if you want the displays to be the same.
>
> Or, the watchers might poll the cache file on their own at certain
> intervals (like when the window is pulled to the front), which would be
> much easier and more logical.

Front? I hardly ever run anything full-screen - and even then, there is
the other monitor off to the side...

-- 
   Les Mikesell
    lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org