[jira] [Resolved] (WICKET-5423) Create IResource based implementation of Native Web Sockets

["Martin Grigorov (JIRA)" <ji...@apache.org>]

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

Martin Grigorov resolved WICKET-5423.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 7.0.0
                   6.13.0

Implemented.
https://github.com/apache/wicket/tree/master/wicket-experimental/wicket-native-websocket/wicket-native-websocket-javax/src/test/java/org/apache/wicket/protocol/ws/javax/app demo app shows how to use it (Jetty 9.x/JSR356 + Wicket 7.x).

https://github.com/martin-g/blogs/tree/master/wicket6-native-websockets also shows the same demo (uses Jetty 9.0 with Wicket 6.x)

> Create IResource based implementation of Native Web Sockets
> -----------------------------------------------------------
>
>                 Key: WICKET-5423
>                 URL: https://issues.apache.org/jira/browse/WICKET-5423
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-native-websocket
>    Affects Versions: 7.0.0
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>             Fix For: 6.13.0, 7.0.0
>
>
> At the moment Wicket Native WebSocket module provides WebSocketBehavior class that may be used by the application to send and receive websocket messages.
> It has the drawback that any message received in a websocket connection requires to get access to the page (IPageManager#getPage(int), PageAccessSynchronizer) to be able to notify WebSocketBehavior #onXyzMessage() methods. Thus WebSocketBehavior is very easy to use but not that well scalable when there is a high traffic in the web socket connection.
> With this ticket I want to introduce an IResource implementation that will provide the same APIs but will not have this drawback.



--
This message was sent by Atlassian JIRA
(v6.1#6144)