Mercurial > pidgin
view doc/plugin-signals.dox @ 25452:6a0304f317cf
I was hoping this wouldn't be necessary, but it seems that the possibility
has increased now that we update the display name in the AB.
If two SOAP requests fail because of outdated tokens for the same server,
it's possible that the second one could fail miserably. That's because both
times, the update request would be made with the original cipher secret.
However, the response for the first request would overwrite this secret,
and the second response would attempt decryption with this new secret
instead of the original.
Now, we queue up the callbacks if a token-update is already in progress.
This results in a single update if there happens to be multiple failures at
a time, and it stops this incorrect decryption problem.
Fixes #8415.
author | Elliott Sales de Andrade <qulogic@pidgin.im> |
---|---|
date | Sun, 15 Feb 2009 02:11:58 +0000 |
parents | e0613cf8c493 |
children |
line wrap: on
line source
/** @page plugin-signals Plugin Signals @signals @signal plugin-load @signal plugin-unload @endsignals @see plugin.h <hr> @signaldef plugin-load @signalproto void (*plugin_load)(PurplePlugin *plugin); @endsignalproto @signaldesc Emitted when a plugin is loaded. @param plugin The plugin that was loaded. @endsignaldef @signaldef plugin-unload @signalproto void (*plugin_unload)(PurplePlugin *plugin); @endsignalproto @signaldesc Emitted when a plugin is unloaded. @param plugin The plugin that was unloaded. @endsignaldef */ // vim: syntax=c.doxygen tw=75 et