Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
8.7.0
-
None
Description
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.
Attachments
Issue Links
- links to