[
https://issues.apache.org/jira/browse/WICKET-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396851#comment-13396851
]
Martijn Dashorst commented on WICKET-4611:
------------------------------------------
Can you explain why this module, and how it relates to wicket-atmosphere? It
sounds a bit strange to have 2 ways to provide push support in Wicket. I know
it is experimental, and welcome different strategies for functionality, but I'd
like to know what your idea is about the future of this module and atmosphere.
> Provide native integration with web containers' websocket support
> -----------------------------------------------------------------
>
> Key: WICKET-4611
> URL: https://issues.apache.org/jira/browse/WICKET-4611
> Project: Wicket
> Issue Type: Wish
> Components: wicket
> Affects Versions: 6.0.0-beta2
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Fix For: 6.0.0-RC1
>
>
> I've played a bit with Jetty's WebSocket support and I've found out that it
> should be fairly easy to integrate it with Wicket.
> The ultimate goal was to create something like Ajax behavior that uses
> WebSocket as communication channel. The result is WebSocketBehavior which
> provides the ability to listen for text and binary messages sent by the
> client and WebSocketRequestHandler which can be used to push messages to the
> clients.
> The client side integration (the JavaScript part) extends wicket-ajax.js so
> it is possible to update Wicket components by pushing them as messages.
> The integration has been extended to support Tomcat 7.0.27+.
> There is also integration with Glassfish 3.1.x but there are some bugs in it
> and it doesn't work for now.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
