asked 2014-01-03 15:20:22 +0200
I have contacts that may be connected to their xmpp account more than once. As an example : Resource A, priority 30, status away Resource B, priority 0, status available
in this case, the contact is "available" (green) in sailfish but should be "away" (orange) as I can see using xmpp clients like gajim or pidgin.
answered 2014-01-03 20:21:22 +0200
My perceived understanding of priorities in XMPP is that 'available' resource is always the one that is considered highest, no matter what priority it has.
Status and priority are not the same feature, and priority is a subset of status. Priority comes into play only when there are at least two statuses of same kind active.
XMPP spec is mostly technical talk but I found this which says it better: http://wiki.xmpp.org/web/Jabber_Resources
EDIT: This proved more difficult than I originally thought. http://www.xmpp.org/rfcs/rfc3921.html#rules
Point 11.1 - 4.1 mentions that available resources are the primary. However it does not mention whether available in that context means just resource online or available status/stanza.
I don't know about Gajim but Pidgin seems to respect the logic that anything that is online and available goes first. Maybe this depends on server software used (OpenFire in my case).
rfc3921 is obsolete, please use rfc6121 :)
The logic for delivering messages is only based on priority, not on <presence><show>whatever</show></presence>. So my conclusion is that displaying presence should also be based on priority. (it's not explicit in the rfc)
kael ( 2014-01-03 21:18:24 +0200 )editYup, just found rfc6121. I think you are correct. :)
There might be a reason why the rot has set in many phone clients... Probably to do with people not messing with settings. Nevertheless, the RFC should be honored or we don't know what to trust, as already happened in my case.
Manatus ( 2014-01-03 21:25:41 +0200 )editAsked: 2014-01-03 15:20:22 +0200
Seen: 234 times
Last updated: Jan 03 '14