Fixed
Details
Assignee
Daniel HenningerDaniel HenningerReporter
Daniel HenningerDaniel HenningerComponents
Fix versions
Priority
Major
Details
Details
Assignee
Daniel Henninger
Daniel HenningerReporter
Daniel Henninger
Daniel HenningerComponents
Fix versions
Priority
Created May 8, 2008 at 10:56 PM
Updated November 13, 2013 at 2:28 PM
Resolved May 9, 2008 at 1:52 AM
With BOSH based implementations, you find yourself left with sessions that "hang around" for a while. In theory browser based apps can just log out, cleaning up the session. However, browsers crash, and the sessions can get "stuck". As a result, you may reconnect and end up having a nickname conflict that you can't get rid of because the old session is still around. What this issue will address is the ability for, if there's a nickname conflict but it's owned by you, allowing you to take over that nickname. (you "kick" the original instance and take it over basically) The original login, if it's a real login, will see a kicked message indicating that they got booted because they logged in from a different location.