view doc/dbus-server-signals.dox @ 13786:5ddde4ad1ca2

[gaim-migrate @ 16198] Fix some places where a closed socket isn't being dealt with correctly. This may be the cause of the high CPU usage that some people have noticed. Most of these were reported by Eduardo Prez. committer: Tailor Script <tailor@pidgin.im>
author Daniel Atallah <daniel.atallah@gmail.com>
date Fri, 26 May 2006 03:26:03 +0000
parents 1ec93dd2f359
children e0613cf8c493
line wrap: on
line source

/** @page dbus-server-signals DBus Server Signals

 @signals
  @signal dbus-method-called
  @signal dbus-introspect
 @endsignals

 <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 tw=75 et