[packagekit] Forked and Threaded

[Robin Norwood]

On Sun, 09 Mar 2008 14:27:40 +0100
Sebastian Heinlein <glatzor at ubuntu.com> wrote:

> Servus,
> 
> I would like to keep the threaded approach for the apt2 backend,
> since I see the following problem with forking: You cannot change the
> cache of the parent process, since all the work is done in the child
> process.
> 
> The search of the apt2 backend is very fast and so isn't an interface
> blocker. In the end I only want to allow to cancel the downloading
> part.
> 
> So Robin, would you please take a look at the forked-dbus-backend
> branch? The decorator should work for you and even simplify your code.
> 
> By the way doesn't it make more sense to exit the main loop of the
> child process right at the beginning? AFAIK this way you don't get
> into the situation that the child processes DBus calls.

Hi,

I've played around with the threaded approach in the forked-dbus-backend
branch, and it seems to be working much better for the yum2 backend.
It's still not quite stable, but it hasn't broken nearly as badly as
the forked version.  I think as long as we're careful to keep
everything yum-ey in a single thread, we might have a winner.  How do
you feel about merging forked-dbus-backend back into the master
branch?  Or I can do it if you agree that it's ready but don't have
time to do it.

-RN

-- 
Robin Norwood
Red Hat, Inc.

"The Sage does nothing, yet nothing remains undone."
-Lao Tzu, Te Tao Ching