Bug 278286 - kopete does not respect jabber resource priority
Summary: kopete does not respect jabber resource priority
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-22 17:34 UTC by Anthony Winslow
Modified: 2013-06-04 16:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 4.10
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anthony Winslow 2011-07-22 17:34:38 UTC
Version:           unspecified (using Devel) 
OS:                Linux

When sending messages to someone who is logged in at multiple locations (multiple resources), kopete will send a message to every resource. This is good behavior.

Once the recipient has responded from a particular resource, that resource should have priority over others, and should be the only resource that recieves messages in a continuing conversation. Other chat clients behave that way, but kopete continues to send messages to every resource.

This may be frustrating for someone who is, say, logged into gtalk on their phone, has gmail open, and is signed in to gtalk with a desktop client - they will recieve 3 notifications every time a kopete user sends them a message.

Reproducible: Always

Steps to Reproduce:
1. Find a friend signed into a jabber account from multiple locations.
2. Send them a message.
3. They recieve the message in multiple locations.
4. They respond from one location.
5. Send them another message.
6. They recieve the message in multiple locations.


Expected Results:  
Kopete should send messages to all locations initially, and once a reply has been recieved, only send to that particular location to continue the conversation.
Comment 1 Pali Rohár 2013-06-04 16:25:52 UTC
This bug should be fixed in KDE 4.10 (svn revision 1328052).