Actually you should already be able to use wicket-push WITH atmosphere (it is a valid cometd servlet).
The advantages would be as Sebastian says: seemless fallback from HTML5 websockets (the push javscript client supports this protocol) and the long polling client. Another design plus is that with push, we are able to implement even more backends than that: We already have the comet, and timer backends, and want to start with a Stomp backend to integrate with: ActiveMQ 5.4 ... http://activemq.apache.org/websockets.html On Mon, Nov 15, 2010 at 10:00 AM, Sebastian <[email protected]> wrote: > Thanks for sharing. I like the graceful Websocket fallback of Atmosphere in > case the server or the client do not support it. > > However it looks like the approach discussed in the blog entry is very > low-level, meaning you have to work with JavaScript directly etc. to > actually do updates (but I may be wrong here). > > wicket-push (which also comes with a cometd implementation) on the other > hand allows you to update page components the type-safe Wicket way by > working on an AjaxRequestTarget. > > Here is an example: > http://wicketstuff.org/confluence/display/STUFFWIKI/wicket-push > > Regards, > > Seb > > > On 15.11.2010 15:06, Josh Kamau wrote: > >> Hi guys, >> >> I came across this. >> >> >> http://jfarcand.wordpress.com/2010/10/07/writing-websocket-application-using-apache-wicket/ >> >> regards. >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Rodolfo Hansen CTO, KindleIT Software Development Email: [email protected] Mobile: +1 (809) 860-6669
