[Psi-Devel] Psi handling of priorities of user presence
norka.lucena at collabworx.com
Wed Nov 2 09:22:09 PDT 2011
Dear Psi developers,
I have noticed that Psi handles priorities of user presence in a non
very intuitive way, which significantly differs from the handling of the
same scenario done by XMPP servers such as OpenFire. Consequently, Psi
displays the wrong presence while the server shows the correct one.
If priorities of two or more resources are the same, Psi uses the last
update from any of those resources as the current user status (which is
not necessarily the correct one).
For example, given a user connected from two resources,
a at b.com/resource1 and a at b.com/resource2, both are priority 5, both being
initially available. If a at b.com/resource1 goes offline, the user a at b.com
is shown by Psi as offline. This is clearly incorrect because
a at b.com/resource2 is still online (as correctly shown by the XMPP server).
Interestingly, this only happens if an observer (another user) is
present in the system. If the observer connects to the system after
a at b.com/resource1 went offline, the user a at b.com is shown correctly as
online (because a at b.com/resource2 is online).
What exactly was your original, intended design for such scenario? Is
this a problem you plan to solve in upcoming versions? Any other comment
on the subject?
Thanks in advance for your feedback,
CONFIDENTIALITY NOTICE - This email is ONLY for the person(s) named in
the message header. Unless otherwise indicated, it contains information
that is confidential, privileged or exempt from disclosure under
applicable law. If you have received it in error, please notify the
sender of the error and delete the message.
More information about the Psi-Devel