view doc/dbus-server-signals.dox @ 25168:27e6ab4ff554

This should fix a sporadic crash? The behavior before was clearly wrong-- there's no need to check that body != NULL twice. This behavior should be better... but this probably shouldn't be a g_return(), since we don't control the data sent to us by the server it shouldn't be considered a programming error if they fail to send us the "Completed" key
author Mark Doliner <mark@kingant.net>
date Thu, 26 Feb 2009 08:14:24 +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