Does the dbus-binding-tool generate signal wrappers for client side by any option?

[Gaurav Roy]

By using :

 dbus-binding-tool --mode=glib-client 

I have been successful in generating Client Side native DBUS method call 
wrappers.
This is cool because it shields client developers from the G_TYPE_... 
stuff.

Is there something similar that shields the clients for registering 
signal handlers too.
To generate a wrapper of similar nature around 'dbus_g_proxy_add_signal' 
& 'dbus_g_proxy_connect_signal'. ?

If the DBUS picks up the signal related information from Server side XML 
registration, then there should be no need to do 'dbus_g_proxy_add_signal'?
But is it always the case?

Gaurav Roy..