Export active loggers

Bug #374342 reported by Seif Lotfy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
[Legacy] GNOME Activity Journal
Status tracked in Trunk
Trunk
Fix Released
High
Siegfried Gevatter

Bug Description

We need to export the active loggers like firefox and tomboy outside the engine. We will pack them all in a new package zeitgeist-loggers and should create a new process zeitgeist-loggers.sh that acts like a semi "datasink" for all active loggers and sends it to the engine datasink.
As for the next couple of weeks it is not necessary for the engine to know its Dataproviders.
This shoudl be done before release.
The positive side about this is that we can create a thread for every logger in the process. This way if a logger drops the engine is not effected. plus working on the engine can be much smoother when less code is in it.

Tags: datasource
Revision history for this message
Seif Lotfy (seif) wrote :

We should send from the zeitgeist-loggers proess to the engine via DBus

Changed in gnome-zeitgeist:
assignee: nobody → Siegfried Gevatter (rainct)
importance: Undecided → High
status: New → Confirmed
Seif Lotfy (seif)
Changed in gnome-zeitgeist:
assignee: Siegfried Gevatter (rainct) → Natan Yellin (aantny)
tags: added: datasources
removed: loggers zeitgeist
tags: added: datasource
removed: datasources
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.