I seem to be unsubscribed from the dbus-list and can’t resubscribe, I’m guessing due to the hard drive meltdown a week ago, so I’ll post the e-mail here:

D-Bus 0.36 is released. Hopefully this will go smoother than the last release but if there are problems please let me know. This release includes numerous bug fixes and a couple of enhancements.

For the low power consumption crowd you can now have the bus match on arguments to avoid those pesky NameOwnerChanged signals from waking up every process.

The python bindings now support match on args and also adds the ability to specify timeouts on calls and explicitly cast to D-Bus types. The much talked about Introspection isn’t done yet but the foundations for
it are already in.

In the GLib bindings we see a lot of bugs being squashed and support for deeply recursive types was added. Watch out, some of the API has been taken private and is no longer exported. It shouldn’t affect anyone but if it does at least you know why.

As usual:
http://dbus.freedesktop.org/releases/dbus-0.36.tar.gz

What is D-Bus?

D-BUS is a message bus system, a simple way for applications to talk to one another.

D-BUS supplies both a system daemon (for events such as “new hardware device added” or “printer queue changed”) and a per-user-login-session daemon (for general IPC needs among user applications). Also, the message bus is built on top of a general one-to-one message passing framework, which can be used by any two apps to communicate directly (without going through the message bus daemon).

Update

I was trying to figure out why hal-device-manager wasn’t getting any signals and finaly realized a couple of hours later that my version of HAL didn’t import dbus.glib to get the mainloop integration. Doh, but it wasn’t a complete waste as I did uncover some other bugs. New release tomorrow morning. I’m also going to write those regression tests for Python.

[read this post in: ar de es fr it ja ko pt ru zh-CN ]