Forums » Help » socket.io and Chrome?

I'm think I'm seeing the Chrome browser buffer up every 5 seconds worth of socket.io state messages emitted from my server, then send that 5 seconds worth of messages to my socket.on callback all at once.

Under the IE browser, my callback fires immediately after each message, multiple times per second, making me think the problem is not in my code.

In other parts of my game, Chrome seems to work great with socket.io. For example, I can press arrow movement keys on the client and instantly see the server logging the input events. No five second buffering there!

Anyone know what might be going on? (I'm new to socket.io and Impact so I might be doing something horribly wrong.)

Any chance you had Chrome minimized before you noticed this sudden "burst" of socket events?

No. Normal usage. And it's not a single burst, it's EVERY 5 seconds, forever.

Socket.io uses different connectivity methods. have you looked at which method it uses to connect on IE and chrome ?
i.e long polling, flash sockets, websockets ..

Maybe you websockets are disabled on chrome ?

The reported socket.io transports are:
Chrome 19: websocket
IE 9: htmlfile

The websocket is broken, the htmlfile works great. Not the maturity level I'd hoped for websockets.

I'm trying to figure out how to override the transport used by socket.io to see if I can force it to work on Chrome.