Something the native client can do but the HTML5 client can't.
In my understanding, the main difficulty here is that we do not have support for multiple sessions per user in Web Access. That is, we heuristically choose which session to reconnect to if multiple sessions are already running on the server (see bug 5060). Killing the wrong session is far more destructive than reconnecting to the wrong session. From my point of view, we have two alternatives: - Letting this snowball into a big project where we add full multi-session support to Web Access. - Only enable this feature in clusters that allow a maximum of 1 session per user (and bail out if the user despite this has more than 1 session running for some reason). Only allowing one session per user seems to be the norm, so I think the latter approach is fairly reasonable, especially considering the stance all major DEs have taken against multiple sessions per user.
