[Pidgin] #9874: XMPP priority changes not obeyed for pre-existing conversation windows

[Pidgin]

#9874: XMPP priority changes not obeyed for pre-existing conversation windows
--------------------------+-------------------------------------------------
 Reporter:  rafi          |     Owner:  rekkanoryo
     Type:  defect        |    Status:  new       
Component:  unclassified  |   Version:  2.5.8     
 Keywords:                |  
--------------------------+-------------------------------------------------
 Pidgin is not properly following shifts in user priorities once
 conversation windows are open.  It is quite easy to reproduce and I tested
 the behavior of two other XMPP clients (Psi & Gajim) to verify that this
 is in fact an issue specifically with Pidgin.


 1. Login with ClientA/home, priority 10 and ClientA/work, priority 5
 concurrently.[[BR]]

 2. Login with ClientB/home.[[BR]]

 3. Open a conversation from ClientB to ClientA and send a message.
 ClientA/home properly receives the message, because it has the highest
 priority.[[BR]]

 4. Keep the aforementioned conversation window open and change priority on
 ClientA/home to 1.[[BR]]

 5. Send a message from ClientB to ClientA again.  ClientA/home again
 receives the message.  It should have gone to ClientA/work because it now
 has a higher priority.[[BR]]


 Basically, it appears Pidgin is routing messages directly to a particular
 resource, making the determination at the time the conversation window is
 created.  I am not sure routing directly to a resource
 (user at domain/resource) is even correct.  If messages are sent to the JID
 itself (user at domain), the server should route messages to the highest
 priority client.  Sending messages specifically to a resource is typically
 an additional option in other XMPP clients, not the default behavior.

 If the intention is to continue routing to specific resources, then Pidgin
 should verify the resource in question is still has the highest priority
 before continuing to send messages to it.  If not, switch the destination
 resource to the one which has the highest.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9874>
Pidgin <http://pidgin.im>
Pidgin