You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2019/04/11 12:07:00 UTC

[jira] [Resolved] (WICKET-6649) Store the applicationName, sessionId and key in WebSocket Text/BinaryMessage and in IWebSocketConnection

     [ https://issues.apache.org/jira/browse/WICKET-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-6649.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 9.0.0-M1

> Store the applicationName, sessionId and key in WebSocket Text/BinaryMessage and in IWebSocketConnection
> --------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-6649
>                 URL: https://issues.apache.org/jira/browse/WICKET-6649
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-native-websocket
>    Affects Versions: 8.3.0
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>            Priority: Minor
>             Fix For: 9.0.0-M1
>
>
> It would be nice if the web socket messages sent by the client (text and binary) bring the application name, session id and registry key. This information could be used when deciding to which web socket connections to send answer. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)