For the server-side code, Socket.IO-Java seems to rely on Jetty's own implementation, so upgrading Jetty might/should be enough (would be if we, at least temporarily, switch to no longer use Socket.IO).
There might be a need to upgrade the client-side too though, because the SWF talks in WebSockets to the server, with the old "-76" protocol rather than the new "-10" version; not sure if someone's working on updating it though (the issue https://github.com/gimite/web-socket-js/issues/82 is tagged with "patches-welcome", and they seem to be waiting for Chrome 14 and Firefox 7 to become "stable releases"); but we could also disable the Flash fallback (I don't know how, but http://socket.io implies that it's possible). On Mon, Aug 29, 2011 at 1:49 PM, Yuri Z <vega...@gmail.com> wrote: > If so, it seems like it poses a real issue for us. Maybe we would have to > replace Socket.IO with other framework, like Comet.d. > > On Mon, Aug 29, 2011 at 2:41 PM, Ruxiao Ma <m...@hcc.im> wrote: > >> If it's because of the incompatibility of different WebSockets protocol >> version it won't work either... >> >> At least, I'm running wiab with use_socketio = false today and used a clean >> copy of chromium. No luck. >> >> On Mon, Aug 29, 2011 at 19:36, Yuri Z <vega...@gmail.com> wrote: >> >> > Maybe we should change the default value of use.socketio fllag in >> > server.config to false? >> > >> > On Mon, Aug 29, 2011 at 12:30 PM, Thomas Broyer <t.bro...@gmail.com> >> > wrote: >> > >> > > On Mon, Aug 29, 2011 at 7:44 AM, Ruxiao Ma <m...@hcc.im> wrote: >> > > > The computer I'm using now is Chromium 15.0.866.0 (build 98596) on >> > > Windows >> > > > XP. >> > > > >> > > > My home computer is using Windows 7 with Chrome dev-channel >> > > (15.something, >> > > > will check when I arrive home tonight). Haven't tried under Linux. >> > > >> > > It's expected that recent versions of Chrome/Chromium no longer work, >> > > this is because Chrome/Chromium has switched to the latest (and now >> > > stable) version of the WebSockets protocol, which is incompatible with >> > > the previous (in-flux) one. See >> > > >> http://blog.chromium.org/2011/08/new-websocket-protocol-secure-and.html >> > > Socket.IO still detects that Chrome supports WebSockets (because the >> > > JS API hasn't changed) but the server-side doesn't speak the same >> > > protocol. >> > > -- >> > > Thomas Broyer >> > > /tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/> < >> http://xn--nna.ma.xn--bwa-xxb.je/> < >> > http://xn--nna.ma.xn--bwa-xxb.je/> >> > > >> > >> > -- Thomas Broyer /tɔ.ma.bʁwa.je/
