view doc/certificate-signals.dox @ 29387:232fcf1755d6

The default state on the MXit server when connecting is Available (with no status message), but Pidgin might be configured to remember the last presence state. So after login, if the presence is not Available or if a Status message has been set then we need to send a Status update packet to the MXit servers. Pidgin also use a HTML-style encoding for the status message. In the situation above they also need to be de-HTML'ified first.
author andrew.victor@mxit.com
date Tue, 26 Jan 2010 14:16:18 +0000
parents e0613cf8c493
children
line wrap: on
line source

/** @page certificate-signals Certificate Signals

 @signals
  @signal certificate-stored
  @signal certificate-deleted
 @endsignals

 @see certificate.h

 <hr>

 @signaldef certificate-stored
  @signalproto
void (*certificate_stored)(PurpleCertificatePool *pool, const gchar *id, gpointer data);
  @endsignalproto
  @signaldesc
   Emitted when a pool stores a certificate. Connect to the pool instance.
  @param pool    Pool the certificate has been stored into
  @param id      Key the certificate was stored under
 @endsignaldef

 @signaldef certificate-deleted
  @signalproto
void (*certificate_deleted)(PurpleCertificatePool *pool, const gchar *id, gpointer data);
  @endsignalproto
  @signaldesc
   Emitted when a pool deletes a certificate. Connect to the pool instance.
  @param pool    Pool the certificate was deleted from
  @param id      Key that was deleted
 @endsignaldef

 */
// vim: syntax=c.doxygen tw=75 et