Stefan Küng wrote:
> Peter McNab wrote:
>
>> There are still some "Invalidating and refreshing folder" messages
>> streaming between "Updating Path" messages in CacheWindow.
>> See attached.
>
> I can't get rid of them completely, I can only reduce them. After all,
> during a checkout, the status of every checked out file changes from
> "unversioned" to "normal", and the watcher has to catch that too.
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?
If it re-crawls for a change notification, what if we used
a simple named mutex to serialize activities?
So the cache would grab the mutex before it starts a crawl,
and TSVN proper would grab the mutex before it started an
update/checkout or other command that would trigger a-lot
of changes.
The cache might just grab and release the mutex (ensuring that
it doesn't start a crawl while TSVN is working but not that TSVN
doesn't start working while it crawls.) But if I understand
how the cache is working correctly, it will notice a file
changed in the middle of it's crawl and it will abort and then
wait for the mutex to become available before re-crawling.
It wouldn't be perfect as it wouldn't handle the command line
client and the locking granularity is pretty big... but it
would pretty well eliminate the cache and TSVN competing
with each other.
Another possibility (if the svn apis let you) would be to have
check to see if the working copy is locked before starting a
crawl.
The problem with this is getting notified when the working
copy is unlocked...
Thanks,
Joseph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Nov 30 06:05:22 2005