[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:  deryni
     Type:  defect  |       Status:  new   
Milestone:          |    Component:  XMPP  
  Version:  2.5.8   |   Resolution:        
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by rafi):

 The problem is, as it stands, priorities basically do not work.  I suspect
 the use case I am concerned with is rather common.  A user is logged in
 from 2 locations during the day: one desktop and another mobile.  When the
 user steps away from their desk, they prefer messages be routed to their
 mobile, then back to the desk once they return.

 Clients with support for dynamic priorities (Psi, Gajim and eventually
 Pidgin) "do the right thing" and support flipping back and forth between
 the destination with the highest priority.  With Pidgin, this is only
 possible if ClientB (from my previous example) is constantly closing and
 reopening the conversation window with ClientA, which does not happen.  I
 think people tend to keep conversation windows open throughout the day.

 If I understand the spec correctly, in the case of equal priorities, the
 server will route to the most recently established/connected resource.  I
 did not see anything about the client having to make these decisions.
 Either way, I really hope to see the current behavior of Pidgin changed.
 The message recipient is specifically setting priorities to decide where
 his messages should go and Pidgin is ignoring this.  I think the use cases
 for the sender to be able to address a specific resource are much less
 likely than following the priorities set by the recipient.

 Ideally I think Pidgin should always send to the highest priority
 resource.  If the resource with the highest priority shifts during a
 conversation, perhaps prompt the sender about it (i.e. Recipient's highest
 priority resource has changed, stay with the existing resource?) and make
 the prompt configurable.

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