zeitgeist team mailing list archive

[Markus Korn <thekorn@xxxxxx>]

I'm not a big friend of the idea to allow someone else than the daemon
itself modify config files like datasources.(pickle|json), because this
would require the daemon to watch-out for changes to all config files it
and its extensions are using.

libzeitgeist and the datahub should instead defer any communication to
the daemon until before the first event is inserted, e.g. the datahub
should register itself as a datasource only once it inserts the first
event. This doesn't necessarily solve the initial issue of this
bugreport (zg slowing down login time) but it's a start. In a next step
we have to make sure that the datahub inserts events as late as
possible, *not during session login*.

-- 
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/772265

Title:
  The datahub starts zeitgeist-daemon on startup

Status in Zeitgeist Client Library:
  New
Status in Zeitgeist Framework:
  New
Status in Zeitgeist Datahub:
  New

Bug description:
  We have been advising distros put zeitgeist-datahub into the autostart
  section for the sessions. This is better in theory because this way we
  only start a native daemon on login and can defer the launching of the
  heavier Python process zeitgeist-daemon.

  Unfortunately zeitgeist-datahub does DBus activation of the zeitgeist-
  daemon on startup so we really don't get the benefits we wanted.
  Bootcharts from Ubuntu 11.04 indicates that ZG eats about 1s on the
  login time and I don't think that is acceptable for ZG in the longer
  run. That is - no catastrophe for 11.04, but we should fix this.

  (a related issue seems to be that the dbus activated zeitgeist-daemon
  seems to launch another datahub instance that then immediately becomes
  a zombie... ? :-/)