Re: [Tracker] New branch for Xesam support in trackerd

[Jamie McCracken <jamiemcc blueyonder co uk>]

On Mon, 2008-04-28 at 11:37 +0200, Philip Van Hoof wrote:
> On Mon, 2008-04-28 at 17:05 +0800, wendy wrote:
> > Hi Philip,
> >
> > I think we should take into account of using the "xesam-glib", which
> > will simplify the implementation of "xesam-support" on tracker. 
>
> Hey Wendy,
>
> Xesam-glib has a few classes that provide an abstract GLib GObject. You
> can implement it and get everything DBus related for free.
>
> Which is nice, indeed.
>
> However. The DBus related things for the Xesam support for trackerd have
> already been done in a very similar way to how xesam-glib works.
>
> For now ain't the code actually doing things asynchronously because none
> of the existing trackerd infrastructure and code is prepared for
> asynchronous operations (there's insufficient locking and data isolating
> in place, SQLite wouldn't cope with multiple threads accessing it, etc).

sqlite 3.5 + is totally threadsafe and multiple threads can access it
safely

though I dont think making it  async is necessary? Surely that would
make the code harder to read and maintain?

to keep the tracker daemon resposive to handling search requests we will
need it to have threads with the main thread dedicated to handling dbus
calls (and shutdown) only (as it is in trunk)

also as tracker is more increasingly used we will want multiple threads
handling requests

> We could indeed solve this with a little queue system and I have last
> Friday converted the DBus frontend to use the DBusMethodInvocation and
> Async=true way of using the dbus-binding-tool (just like xesam-glib). 

queueing is essential

jamie