Re: [Tracker] Database access abstraction

[Martyn Russell <martyn imendio com>]

Jamie McCracken wrote:
> On Thu, 2008-11-06 at 16:11 +0100, Philip Van Hoof wrote:
> > On Thu, 2008-11-06 at 09:39 -0500, Jamie McCracken wrote:
> > > its not that clear cut
> > >
> > > firstly, pausing the indexer is an async process and does not have to be
> > > synchronous at all so there is no round trip with direct access.
> > Pausing the indexer right now has to be (and is performed) synchronous.
>
> it can and should be async
>
> sqlite will release its locks when its ready so there is no need for it
> to be synchronous

Can be yes. But it doesn't make sense to.

The daemon can do nothing while it waits for the indexer to finish
writing to the database. It is better to synchronously wait for the
indexer and let DBus tell clients that the service is busy than just
keep queuing up requests if we get too many I think. If we do it
asynchronously, we currently would just have a huge delay between the
user requesting information and actually it doing something OR, they
would get a response saying the service is busy from DBus internally
timing out requests. Maybe this is done for async requests too - but I
don't think so.

-- 
Regards,
Martyn