See this page for instructions on how to use Flyspray: http://psi-im.org/wiki/Flyspray
Please Note!
Please do not create tasks here without discussing your bug or feature request on the forums or groupchat psi@conference.psi-im.org, *and* getting explicit confirmation by a developer to add it to flyspray.
Please Note!
Please do not create tasks here without discussing your bug or feature request on the forums or groupchat psi@conference.psi-im.org, *and* getting explicit confirmation by a developer to add it to flyspray.
FS#827 - Going offline with a status message from Psi doesn't send the status to MUC's
Attached to Project:
Psi Jabber Client
Opened by Norman Rasmussen (normanr) - Sunday, 20 April 2008, 13:14 GMT-5
Last edited by Martin (martin) - Sunday, 20 April 2008, 13:20 GMT-5
Opened by Norman Rasmussen (normanr) - Sunday, 20 April 2008, 13:14 GMT-5
Last edited by Martin (martin) - Sunday, 20 April 2008, 13:20 GMT-5
|
DetailsI tracked this one down to psiaccount.cpp's logout method, it seems that the final unavailable broadcast presence is sent in logout, then a 100ms delay for the server to process, then client->close is called. client->close sends an unavailable presence for each groupchat the client is in, and then closes the stream.
Now if the same rules apply for broadcast presence and directed presence then the muc presences should be sent _before_ the 100ms delay. Should they be sent with the proper status message too? muc log: http://conference.psi-im.org/psi(at)conference.psi-im.org/2008/04/20.html |
This task depends upon