Re: [Tracker] Moving crawling to the indexer



On Mon, 2008-11-10 at 16:45 +0000, Martyn Russell wrote:
My idea was that the daemon, which is _ALWAYS_ running, should hold all
state information and the indexer shouldn't since it is temporary, not
always running. By state information, I mean:

- Are we in READONLY mode
- Are we running?
- Are we indexing for the first time?
- Are we merging?
- Are we paused manually (by the user)?
- Are we paused for IO (due to Monitor events).
- Is the disk full?
- Is the battery low?
- What state are we in generally (i.e. INDEXING, IDLE, etc).
- How many items have we processed?
- How long have we been indexing?
- How long before we are finished (estimated)?

I agree that it makes sense for the daemon to hold all state
information. The indexer is just a worker process, the daemon should be
in charge of the policy / the decisions as it's always running.

JÃrg




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]