[
https://issues.apache.org/jira/browse/WICKET-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810537#comment-16810537
]
ASF subversion and git services commented on WICKET-6649:
---------------------------------------------------------
Commit b23ed1160ec1c3660b8e21cbe1d3dde6217a6be3 in wicket's branch
refs/heads/WICKET-6649-downport-for-wicket-8.x from Martin Tzvetanov Grigorov
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=b23ed11 ]
WICKET-6649 Store the applicationName, sessionId and key in WebSocket
Text/BinaryMessage and in IWebSocketConnection
Downport of 12b1fb227564c22f4887dea23610be7cb8c5d977 for Wicket 8.x.
It manages to trick maven-clirr-plugin (binary compatibility checker) by using
dummy values for Application, session id and IKey
> 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
>
> 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)
