[dbus-cplusplus-devel] dbus-c++ multi threading and setting default_dispatcher

[Kiran P. <kir...@gm...>]

Hi,

I am using dbus-c++ with glib eventloop integration. The examples
provided with dbus-c++ always uses BusDispatcher as a global variable.
I am using multi threaded application which uses dbus-c++ calls across
threads. Currently in every thread I am locally creating creating a
DBus::Glib::BusDispatcher variable( on stack ) and setting the
default_dispatcher. The dispatcher will be destroyed as the thread
completes. Is this advised ?

The scenario I am worried about is two threads simulataneosuly
creating DBus::Glib::BusDispatcher( as local variable) and setting
default_dispatcher which affects the other thread. Is dbus-c++
expected to be used across threads ? Is default_dispatcher the only
way to set a dispatcher ?

An additional query: Is the sourceforge dbus-c++ repo maintained any more ?

Thanks for reading,
Kiran.