Stefan Küng wrote:
>On 11/30/05, Joseph Galbraith <galb@vandyke.com> wrote:
>
>
>
>>Do I understand correctly that when the cache gets a file
>>change notification, it re-crawls that section of the file
>>hierarchy? Or does it only re-get status on files that
>>are reported as having been changed?
>>
>>
>
>It recrawls the folder where the modified file is in. That's because
>svn_client_status() always gets the status of all files in a folder,
>no matter if you specify the folder of a file within in the parameters
>(it just will filter out the status info of all other files if you
>don't specify the folder).
>
>
>Stefan
>
>
>
A recent change has certainly reduced the number of "Invalidate..."
messages. Some time ago, I mused on the list about delaying operations
as a result of receiving notifications, probably on a false premise but
there might be some merit in the following.
On update or checkout I expect there are multiple notifications firing
off as files are written or touched. Instead of kicking off the
invalidate action following a file write, if a single re-triggerable
timer was fired instead and re-triggered for each subsequent
notification that occurs before the timer expires then many redundant
operations might be avoided. On expiry the timer triggers the Invalidate
process. The timer value might be an arbitrary 1 sec and fetched from
the registry to allow post deployment adjustment.
Does this make sense?
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Nov 30 11:47:07 2005