D-BUS getting into shape

The last few days saw a couple of threads on the dbus mailinglist about topics we KDE users got used to love in DCOP. For example how to start browsing for interfaces on applications connected to the bus, in D-BUS terminology called introspection, how to know which session busses are currently active for a user and how to work with users session busses from the system bus.

The last two features are known to DCOP commandline client users as

dcop --all-sessions

and

dcop --all-users --all-sessions

where especially the second form is very nice to have in administrative scripts to inform the users about stuff going on, for example telling them via KNotify that the system is about to reboot and they better save or be sorry, or to save and logout all KDE sessions for those users who ignore you anyway :)

And as a personal note to the introspection thingy: if you have introspectable objects you are supposed to register one as a startingpoint at the object path "/" (the root of the path namespace), which is unfortunately not documented yet. (The Qt3 bindings API DOX do, but they in turn do not provide an easy way to generate introspection data yet)