View Single Post
Posts: 96 | Thanked: 107 times | Joined on Aug 2011
#20
Originally Posted by nicolai View Post
No, I don't want to configure khweeteur, because at the moment,
khweeteur isn't running, but I still get notifications about
new tweets, so someone starts khweeteur from the
background.
Woodchuck starts the Khweeteur daemon periodically. That's the point of Woodchuck--it schedules network transmissions periodically. Because Khweeteur registered network transmissions with Woodchuck, Woodchuck starts it when an update should be performed.

Note that the notifications are not displayed by a running instance of Khweeteur (i.e., if you click on a notification, Hildon may need to start Khweeteur): they are standard freedesktop notifications that can be shown even if the application is not (or no longer) running.

Originally Posted by nicolai View Post
In khweeteurs preferences dialog, I disabled the "use daemon"
option. I thought this would be enough to disable khweeteur
fetching new tweets in the background.
But they still show up.
The "use daemon" option means: the Khweeteur daemon always runs in the background and periodically checks for updates (whether you are using WiFi, cellular or even roaming).

When using Woodchuck, the Khweeteur daemon is only started when necessary and quits when there is nothing left to do thereby freeing memory. Further, Woodchuck is aware of the connectivity.

Originally Posted by nicolai View Post
Ok , this may help, but I still don't understand who
fetches the new tweets while khweeteur and the khweeteur
daemon isn't running.
Woodchuck starts the Khweeteur daemon periodically and tells it to fetch updates, which is what Khweeteur requested. You can think of Woodchuck as cron++.

Originally Posted by nicolai View Post
The main concern is:
imagine a user installing khweeteur and he want to disable
it from running in the background. He opens the preference
dialog, disables "use daemon" option, but he still
gets notifications. Even after he closed the kwheeteur applcation.
Ok. This is a good point. I'll come up with a patch to improve Khweeteur in this regard.
 

The Following 2 Users Say Thank You to neal For This Useful Post: