3 ms·
> It might actually introduce more lag to first check for websockets, and if unavailable, fall back to long-polling. Socket.IO works the other way around since
by pygy_ 12y ago
> It might actually introduce more lag to first check for websockets, and if unavailable, fall back to long-polling.
Socket.IO works the other way around since v 1.0, thanks to Engine.IO. It starts with long polling and tries to upgrade to WebSocket or Flash sockets if possible.
- nnain 12y agoThat's good to know. And Socket.IO could move back to WebSocket-first approach, once the technology becomes more pervasive. It's still a task to set up Socket.IO with Python though. Don't know how nice it plays with Node.js, but I'm happy moving to Go instead.