Hey,

I have to admit I haven’t looked at Tracker yet (so maybe once I see
it I may change my opinion), but at the moment my idea is that once
Tracker supports events (so that we can store everything in there and
don’t need to keep events in our own database, which wouldn’t work
performance-wise given the sort of queries we have) we should switch
over to it.

With that approach I’d see Zeitgeist kind of as an “extension” to
Tracker, where it’s functions would be on one side, the logging of
events, and on the other providing a high-level D-Bus API to easily
access events and to get relationships between them (Seif’s magic);
this way we get to keep a very simple to use API but applications
needing more advanced stuff (or maybe requiring more fine-grained
control on what to fetch for performance reasons) have the chance to
query Tracker directly. What are your thoughts on this?

This Tracker stuff would probably be something to discuss at the
end-of-the-year Hackfest (if we get to do it - I hope so), I just
thought I'd say this now before someone gets the idea to implement
some weird query system in Zeitgeist :).

What I think we really need to decide now is how we want to represent
events and items (when returned by FindEvents et all).

-- 
Siegfried-Angel Gevatter Pujals (RainCT)
Ubuntu Developer. Debian Contributor.

_______________________________________________
Mailing list: https://launchpad.net/~zeitgeist
Post to     : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp

Reply via email to