Priority in Jabber
#After I managed to finally get my Jabber+gadu-gadu mix working both on my phone and #computer, the time has come to focus on cooperation of those two devices.
XMPP lets us to log into our jabber account with multiple clients at once. This is both useful (you don’t get kicked out from network because of some other attempt to log in) and potentially uncomfortable (when you’ve got two clients open you never know where the incoming message will come to).
For that reason, the ‘priority’ has been developed. This is a number from range of -127 to +127 sent to the server together with status change. In psi you can add a priority value to every preset status (you can also set it manually every status change). This way I can setup such statuses (#should it be written like that or with latin form ’stati’?):
feel like talking -> 100
online (by the keyboard) -> 100
away (short time) -> -50
eXtended away (XAFK) -> -100
and consequently if my mobile client (I’m using Slick – it allows me to set up one priority value for all statuses) is set to priority 75 it receives my messages only when I’m away or XAFK (i.e. when psi has lower priority than Slick). When I come back to keyboard and change status to online – the messages will come to Psi!
What’s more, I can also change priority value of my mobile client to -75 – then I will receive IM on mobile only when XAFK. That can be useful when I inform my interlocutor I’m going to be away for some time (so I’ll see his/her messages on screen after I come back), but it happens I have been away for longer time than I said I would. That way I’ll receive messages only after psi automatically changes my status into XAFK, so I can read all those ‘r u there?’s.
#The only thing I’m still fighting with is gadu-gadu status. Even when phone has #reater priority, transport imports status of Psi. The only moment it imports status #of phone is… when I go offline on Psi 
#But this probably has nothing to work with priority, ’cause the rest works well!
Leave a Reply