D-Bus 1.0 "Blue Bird" Released

D-Bus 1.0 ("Blue Bird"), the Freedesktop.org inter-process messaging system has just been released. A collaborative effort between industry and open source developers, D-Bus was created to allow arbitrary applications to easily communicate with each other and exchange data. An additional system daemon allows for communication with system services. D-Bus is known to work on all Unix platforms and has also been ported to Mac OS X, while a Windows port is in progress. This makes D-Bus the ideal messaging system for KDE 4.

This first D-Bus major-release will maintain backwards protocol compatibility throughout its entire lifecycle and, just like KDE, its library will maintain API and ABI compatibility until the next major release. The low level library is toolkit agnostic and only depends on an external XML library but many bindings to higher-level toolkits are available, such as Java, glib and Python.
The Qt bindings are available as part of Qt since version 4.2.
"We're hoping that the Qt bindings to D-Bus will allow application and library developers to easily extend their software into this world of exchange of information", says KDE developer Thiago Macieira, who worked extensively on QtDBus at Trolltech. "We've designed the API under the familiar Qt style and we've made it similar to what KDE developers already knew in DCOP, so as to make the transition easier".
D-Bus-Maintainer John Palmieri adds: "The high quality of the Qt4 D-Bus bindings shows how flexible D-Bus is in fitting into native environments. In turn the participation of the Qt4 binding team in the development of D-Bus 1.0 has helped bring this release to a quality that would not have been achieved without their involvement".

While KDE 3 already uses D-Bus to talk to HAL and Avahi, in KDE 4, D-Bus has completely replaced DCOP as the IPC System of choice for KDE. Its use is also growing, with Kopete recently announcing the initial support for Telepathy/Tapioca, via D-Bus, and the accessibility developers studying using it too.

"I really consider this release as a major milestone for KDE 4, since we're now using it everywhere", says Solid developer Kévin Ottens. "Having strong guarantee about compatibility is really important for an IPC system like this, and that's exactly what D-Bus 1.0 offers us". D-Bus serves as infrastructure for Solid to communicate with system services.

Dot Categories: 


by Michaël Larouche (not verified)

D-Bus simply rocks. The Qt bindings are really much easier and cleaner than the old KDCOP interface.

I still remember the time when I was working on Solid and compiling Qt bindings directly from D-Bus CVS was a pain ;)

by cartman (not verified)

They are still at some 0.6x version right?

by Thiago Macieira (not verified)

Kevin (not Kévin) can probably answer better, but I don't think they've seen much work in recent times. They should still be working for the stuff you may need to do with KDE3 code.

by Kevin Krammer (not verified)

I haven't had time to keep them up to date with D-Bus changes. Since the 1.0 release keeps the API stable, I am planning to get the bindings backport compatible again.

However, I haven't yet decided what to do about the issue of more complex datatypes, since the Qt4 bindings code can't be easily backported as its QVariant is way more powerful than Qt3's

My personal goal is to be able to use the Qt3 bindings for implementing any D-Bus interface we might come up with as part of the Portland DAPI efforts.

Any help welcome :)

by ht (not verified)

Anyway to get dbus 0.9x working with qt3 instead of having to have a seperate dbus-qt3-0.62 package? Some patch perhaps?

by Kevin Krammer (not verified)

My system's D-Bus version is 0.94 and the my bindings in SVN seem to work (i.e. compile and the simple example-client works)

I'll have to check more thoroughly later today

by André (not verified)

Well, mine don't. That is: stuff compiles, but things like notifications of plugging in a USB stick don't. :-(

by Kevin Krammer (not verified)

Could you send me the code you are using?

I am not sure I did any testing with D-Bus signals yet, but I think they should work.
Maybe I tested with the OwnerChanged signal, but it has been to long ago to be sure :(

by DarkVision (not verified)

Have you tried the QT3-bindings from here: http://ranger.befunk.com/fink/

I had the same issues with the "official" QT3-bindings. Using the above sources with DBus 1.0/HAL 0.5.7 and KDE 3.5.5 seem to work fine here...