I kindly wonder if there could be plans to make push/Atmosphere/WebSocket more "first class" in Wicket 7 than 6. Since we've been using wicket-atmosphere quite intensively in a few projects.
Since Servlet 3.0 is minimum anyway, which means at least Comet (and hopefully WebSocket) is supported on all containers that runs Wicket 7. In theory this means atmosphere configuration in Wicket 7 is uniform (container-independent). Upgrading to atmosphere 2.0 (currently pre-release) will be one way. Using Atmosphere with Wicket *and* Shiro (as of 6.9.1) requires coding an AtmosphereHandler manually. This configuration can be simplified or the appropriate handler provided by Wicket. HttpsMapper as of 6.9.1 didn't recognize WebSocket. All around compatibility between Wicket's SSL and Atmosphere support can be improved. During my usage I filed several tickets about wicket/atmosphere : * https://issues.apache.org/jira/browse/WICKET-5279 * https://issues.apache.org/jira/browse/WICKET-5282 * https://issues.apache.org/jira/browse/WICKET-5280 * https://issues.apache.org/jira/browse/WICKET-5281 * https://issues.apache.org/jira/browse/WICKET-5134 * https://issues.apache.org/jira/browse/WICKET-5200 * https://issues.apache.org/jira/browse/WICKET-5135 probably others Hendy -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket7-Core-support-for-server-side-push-WebSocket-via-Atmosphere-tp4660503.html Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.
