Hi all, I have sent this Review Request #19355 <https://reviews.apache.org/r/19355/>providing Atmosphere integration.
I hope you liked it, specially Vicente Best regards! 2014-03-05 7:41 GMT+01:00 Vicente J. Ruiz Jurado <v...@ourproject.org>: > El 04/03/14 20:42, Pablo Ojanguren escribió: > > Hi all, > > > > As long as the Jetty 9 upgrade has stop Wiab from using Socket.IO, I am > > trying a solution that was suggested in a previous discussion: atmosphere > > framework. > > > > They state that Atmosphere server component works with Socket.io clients > > without any change, so I am focus on that. ( > > > https://github.com/Atmosphere/atmosphere/wiki/Getting-Started-with-Socket.IO > > ) > > > > I've integrated the framework and implemented analogue clases for > > Connection, Channel... in ServerRpcProvider.java. And I replaced the old > > servlet matching "/socket.io" with a new atmoshphere handler. > > > > Now ,in order to test, I would like to know how the websocket to > > socket.iofall-back works. Is it just client logic staff? > > > > Can anyone help me on this? > > > > Thanks in advance, > > > > Pablo > > > > Thanks Pablo, for work on this. > > And yes, normally it's only client logic. Wiab Server allows the two > options/servlets (in ServerRpcProvider), and webclient tries first the > standard websocket, and if fails tries socketio java library (see > WaveWebSocketClient). > > I think that probably you have to patch WaveSocketFactory also to remove > old Socketio.java dependencies (in order to use the new socketio.js > version). > > By the way, I usually disable websocket in the browser in order to test > these other connectors. > > BR, > -- > Vicente J. Ruiz Jurado >
