Mercurial > pidgin.yaz
view doc/dbus-server-signals.dox @ 30289:ca60dd3812fa
applied changes from 8b6590428d8180cc466c8916f81aec2c8961fbd1
through 1f5f812e500972cfb805d2cf0b3bc423cf2b7f3f
This hack to manually handle X-GOOGLE-TOKEN an X-FACEBOOK-PLATFORM shouldn't be
needed now; avoiding them was masking the problem, since we should be prepared
for a server to offer any number of arbitrary mechs which we may or may not
be able to handle.
author | Evan Schoenberg <evan.s@dreskin.net> |
---|---|
date | Tue, 04 May 2010 02:10:02 +0000 |
parents | e0613cf8c493 |
children |
line wrap: on
line source
/** @page dbus-server-signals DBus Server Signals @signals @signal dbus-method-called @signal dbus-introspect @endsignals @see dbus-server.h <hr> @signaldef dbus-method-called @signalproto gboolean (*dbus_method_called)(DBusConnection *connection, DBusMessage *message); @endsignalproto @signaldesc Emitted when a dbus method is going to be called. @param connection The DBus connection. @param message The DBus message. @return TRUE if signal handler handled the method. ??? @endsignaldef @signaldef dbus-introspect @signalproto void (*dbus_introspect)(GList **bidings_list); @endsignalproto @signaldesc ??? @param bindings_list ??? @endsignaldef */ // vim: syntax=c.doxygen tw=75 et