Hi, I think Atmosphere provides a bit more than what Play has. Atmosphere falls back from WebSocket to Server Side events/Long polling/Streaming if any of those is not supported by the browser and/or server. Play (version 2.0.4 is latest at the moment) has modules for WebSocket or Comet but not combined or with fallback support!
Wicket also has WebSocket-only module - wicket-native-websocket ( http://wicketinaction.com/2012/07/wicket-6-native-websockets/). But as its documentation ( https://cwiki.apache.org/confluence/display/WICKET/Wicket+Native+WebSockets) says it will work only when WebSockets are supported by both the browser and the server. Just like Play's WebSocket support. On Wed, Nov 14, 2012 at 8:08 AM, pkc <[email protected]> wrote: > The atmosphere support is "experimental" right? I just migrated from 1.5 > to > 6.2 and used the wicket atmosphere support but I'm having issues where > pushes sometimes stop working. I thought I found a way around it by > turning > on atmosphere broadcaster caching and message length checking but then I > got > strange behavior where other open browsers would get data meant only for a > single client. I may post a bug but I don't quite understand all the > atmosphere settings. I wish it was a clean and simple as Play 2.1 > Framework > but that is a stateless framework. > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-6-and-wicket-push-tp4653766p4653864.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
