Peter Clifton pcjc2 at cam.ac.uk
Thu Oct 12 08:28:52 PDT 2006


I'm in the situation where I need to provide dbus support in an
application, where the GUI front end of the application is pluggable,
and can either be GTK, Lesstif, or other. Each has its own mainloop and
way of doing things.

I've currently got GTK only support working. The code is very simple,
there are only two methods.

Is there a standard solution for coding a more generic implementation
using the libdbus C API on its own?

All the pluggable GUIs in the application can be requested to provide
timer callbacks, and file descriptor monitoring callbacks.

What would be really nice would be an API, slightly higher level than
the RAW C API, but providing asynchronous functions via a function
pointer based callback system. (Perhaps marshallers or similar would
still be needed).

Setting up this API would require the app to register whatever
file-descriptor and timer callbacks that the dbus part asks it to, and
the rest should be simple. ^TM

I was wondering if we could use a code generator of sorts to provide the
glue, much as dbus-binding-tool does for the glib stuff.

Where do the DBUS people stand on this type of problem... I need a main
loop independent DBUS library, which is ideally a little friendlier to
use than raw libdbus.


Peter Clifton

More information about the dbus mailing list