[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Very long time to crawl WC.

From: Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com>
Date: 2005-12-01 16:42:42 CET

On 12/1/05, Stefan Küng <tortoisesvn@gmail.com> wrote:
> How it's currently done:
> * notification arrives
> * crawler has path of notification in queue
> * crawler starts with the first path in the queue
> * crawler fetches status of path
> * crawler checks queue for the same path it just crawled
> - if same path is in the queue again, remove it from the queue

Forgive my ignorance, but is it possible to do either of the following:

A. If it is a TSVN oeration that triggers the notifications then let
TSVN signal the cache to ignore the WC until done (with a suitable
timeout should TSVN crash before the operation is done and a final
'all clear' is signaled to the cache).

B. Have the cache 'detect' that a large WC operation is underway and
suspend (re)crawling that WC for a suitable amount of time.



   // \\ @@ "De Chelonian Mobile"
  / \_/ \/._) TortoiseSVN
 <\_/_\_/ / The coolest Interface to (Sub)Version Control
  /_/ \_\ Check out http://tortoisesvn.org

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Dec 1 16:58:02 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.