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 <[email protected]> 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 <[email protected]> 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 <[email protected]> > > wrote: > > > > > On Mon, Aug 29, 2011 at 7:44 AM, Ruxiao Ma <[email protected]> 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/> > > > > > >
