Re: [Tracker] Revisiting indexer/daemon architecture

[Ivan Frade <ivan frade nokia com>]

Hi!

El mar, 10-03-2009 a las 19:56 +0100, ext Carlos Garnacho escribiÃ:
> Hi all,
>
> Solution
> ========
> We feel it would be better to have the write functionality of the
> indexer back to the daemon, and make it just hand the metadata
> information to the daemon so it's able to store it.
>
> As for the communication medium between the daemon and the indexer, it
> has to be compact and fast, so sending turtle files through a pipe
> sounds quite optimal.
>
> This architecture change would also ensure that the part that is
> responsible of storing metadata and monitor external sources is always
> kept alive.
>
> So summing up, these would be the roles:
>
> trackerd:
>      - Database read and writes
>      - File system monitoring
>      - Importing metadata to the database using the TTL file format
>      - handle remote/virtual data

I would move "File system monitoring" also to the indexer, so all the
functionality related with the File system is in the indexer.

Tracker-indexer will be just one provider of information, that push into
tracker data about the filesystem, exactly in the same way evolution is
an information provider that push information about emails.


After these changes, we will have

1) A daemon that _only_ stores information and answer queries, i.e. a
"generic" store but optimized for nepomuk. 

2) Information providers like evolution/kmail for email, indexer for the
filesystem, and maybe in the future a RSS monitor.

3) Applications pushing data directly into tracker (a plugin in Pidgin
saying "this contacts has sent me this file", an RSS reader setting the
"isRead" flags in the Feed entries...).


Regards,

Ivan

> _______________________________________________
> tracker-list mailing list
> tracker-list gnome org
> http://mail.gnome.org/mailman/listinfo/tracker-list