view doc/imgstore-signals.dox @ 24536:c457c635eb8f

Two functional changes here: 1. The default error case for unknown errors on yahoo now uses PURPLE_CONNECTION_ERROR_OTHER_ERROR instead of PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED. This change was made because it's logical. 2. The unknown yahoo error with error code "0" now uses PURPLE_CONNECTION_ERROR_NETWORK_ERROR instead of PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED. This change was made because this error doesn't seem to be fatal, and we want the account to be reconnected, but normally AUTHENTICATION_FAILED errors are fatal and should not be reconnected Specially this makes yahoo accounts auto-reconnect when we get the error "Unknown error number 0. Logging into the Yahoo! website may fix this." I know we think we fixed this with that change to send the timeout or keepalive much less often, but I'm still seeing a lot of disconnects for it and I have a strong suspicion that they're not actually fatal errors. Refs #5223

/** @page imgstore-signals Image Store Signals

 @signals
  @signal image-deleting
 @endsignals

 @see imgstore.h

 <hr>

 @signaldef image-deleting
  @signalproto
char *(*image_deleting)(const PurpleStoredImage *img);
  @endsignalproto
  @signaldesc
   Emitted when a #PurpleStoredImage is about to be destroyed.  This allows
   for what amounts to weak references.  Code can hold onto a pointer to
   the PurpleStoredImage without actually "holding" a reference.  They can
   then use a signal handler to let them know when their img is about to
   be destroyed.
  @param img The image about to be destroyed.
  @note It's not possible to purple_imgstore_ref() img to save it.
 @endsignaldef

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