DBus Threading in a Late-loading module

[Thiago Macieira]

Havoc Pennington wrote:
>It certainly is not easy to mix multiple "frameworks" like GTK and Qt
>right now; the exact same problem we're talking about for DBusConnection
>was recently discussed on gtk-devel-list with respect to the X display.
>GDK effectively forms a "binding" for the X display, and someone was
>attempting to allow both GTK and Qt to use the same Display*.
>
>I'm certainly open to fixing this but I'm not sure what we can do.

Hmm... that's a difficult question.

I initially proposed that we enforce a global mainloop library that 
toolkits have to use.

However, this will not make bindings to toolkits that are "more closed" 
like Java (which is no longer using libdbus-1, but was at a point) use 
such a mainloop.

So we're at an impasse.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20070404/78ffae16/attachment.pgp