You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Thomas Heigl (Jira)" <ji...@apache.org> on 2020/03/20 15:47:00 UTC

[jira] [Commented] (WICKET-6761) Support multiple connections to the same websocket resource from a single session

    [ https://issues.apache.org/jira/browse/WICKET-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063465#comment-17063465 ] 

Thomas Heigl commented on WICKET-6761:
--------------------------------------

I created a PR that adds a token to a connection: [https://github.com/apache/wicket/pull/417]

It is a quick draft and feedback would be appreciated.

> 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)