view doc/dbus-server-signals.dox @ 22238:4cc1dfbc499b

Get rid of yahoo_privacy_check and use purple_privacy_check directly. I think the former function may have done stuff in days of yore, but now it's purpose is only to call purple_privacy_check then print a debug message with the result. The debug message doesn't seem overly useful to me... does anyone think it's important? If so, why? And if we really want that debug message, could we just add it to purple_privacy_check()?
author Mark Doliner <mark@kingant.net>
date Thu, 31 Jan 2008 22:58:11 +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