Secondly, the daemon is running with the uid of the current user. Any
application can kill the daemon anytime they need. The only work Quit
does it to make the application easier to kill the daemon.
We have to trust the applications not using Quit.
--
You received this bug notification because y
2010/12/15 Seif Lotfy <690...@bugs.launchpad.net>:
> yes, but what about my pending requests?
> are they all gone?
> ah you mean during an async
Zeitgeist only handles one request at a time, so the Quit will be
alone. The next (queued or not) request should wake it up again.
--
You received t
Public bug reported:
We had the following discussion on IRC
-
seiflotfy, so, any app can quit the zeitgeist daemon via dbus?
abner, yes
:)
seiflotfy, hmmm, why?
abner, dunno :P
abner, i really dunno why i put that
* abner asks God: Why?
u dont have to cover it though
abner, act
So the final consensus is that the parameter s is any randomly chosen
identifier for an application.
* GetBlacklists() -> ({sE})
* AddBlacklist(sE) --> Changed(sE)
* RemoveBlacklist(sE) --> Changed(sE)
I changed the name to Blacklist instead of Template for the method names
as it sounds better a
** Changed in: zeitgeist-dataproviders
Importance: Undecided => Medium
** Changed in: zeitgeist-dataproviders
Status: New => Confirmed
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Data-Sources.
https://bugs
Public bug reported:
I had a talk with thansen which is packaging the zeitgeist engine and
dataproviders for gentoo. When I provided him the tarball of version
0.1.0.0 without the release, he was quizzed if the official release
would also have 0.1.0.0 ?
It s better if we start from 0.2.0.0
** Af
6 matches
Mail list logo
