On 28 April 2011 14:24, Markus Korn <thek...@gmx.de> wrote:
> 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.
I am not suggesting that clients modify anything. That would be very
racy. I am suggesting that clients have access to an API that reads
and parses this file under the hood (ie. the file is considered
internal private "API" to Zeitgeist, but dedicated libs are allowed to
I think we may wanna move in this direction too anyway if/when we
enable WAL on the main db which can allow clients direct read-only
access to the db (still through our APIs ofcourse, but avoiding the
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
The datahub starts zeitgeist-daemon on startup
Status in Zeitgeist Client Library:
Status in Zeitgeist Framework:
Status in Zeitgeist Datahub:
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... ? :-/)
Mailing list: https://launchpad.net/~zeitgeist
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp