[ https://issues.apache.org/jira/browse/WICKET-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071539#comment-17071539 ]
ASF subversion and git services commented on WICKET-6761: --------------------------------------------------------- Commit 904371dccc5921b42813fe15ae59c21880301419 in wicket's branch refs/heads/wicket-8.x from Thomas [ https://gitbox.apache.org/repos/asf?p=wicket.git;h=904371d ] WICKET-6761 Multiple websocket connections from the same session (#417) * WICKET-6761 Add optional `resourceToken` to support multiple websocket connections from the same session * WICKET-6761 Add demo page for websocket resources with multiple tabs * WICKET-6761 Fetch websocket connection on each iteration to showcase issue with multiple tabs * WICKET-6761 Mount demo page and increase executor pool size for multi tab demo * WICKET-6761 Rename `resourceToken` to `connectionToken` (cherry picked from commit 5cce0b148a0cac9cc4d8eb685d8569e84e32eab0) > Support multiple connections to the same websocket resource from a single > session > --------------------------------------------------------------------------------- > > Key: WICKET-6761 > URL: https://issues.apache.org/jira/browse/WICKET-6761 > Project: Wicket > Issue Type: Improvement > Components: wicket-native-websocket > Affects Versions: 8.7.0 > Reporter: Thomas Heigl > Assignee: Martin Tzvetanov Grigorov > Priority: Major > > It is currently not possible to connect to the same websocket resource > multiple times from the same session because the connection is stored with a > key using only the name of the resource (ResourceNameKey). > If a user opens additional browser tabs, only the newest connection survives > in the connection registry. > This could easily be solved by adding some kind of optional token such as a > UUID to the websocket connection and use both resource name and token as a > key. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)