dbus-glib: a server with lots of objects

[Neal H. Walfield]

At Mon, 9 May 2011 09:56:56 +0100,
Simon McVittie wrote:
> 
> On Mon, 09 May 2011 at 10:08:10 +0200, Neal H. Walfield wrote:
> > Is it possible to listen to all object paths using the dbus-glib
> > bindings?  What is the best way to accomplish this in a program that
> > already makes extensive use of dbus-glib?
> 
> As I said on #dbus: if you must stick to dbus-glib, you can use
> dbus_connection_register_fallback (part of libdbus, but dbus-glib connections
> are implemented via libdbus connections, so you can mix the two if you're
> careful). dbus-glib does not have a higher-level API for this.

Is there a way to reinject the message in dbus-glib?  In the fallback
method, I'd like to register a gobject using
dbus_g_connection_register_g_object and then have dbus-glib do the
demuxing, delivery and reply.  I'd like to avoid manually demuxing the
messages using the low-level API since dbus-glib already provides this
functionality.

Thanks,

Neal