3 ms·

If you could do this over again, would you still choose socket.io for websockets, or would you go with something else like PusherApp?

• dodger 15y ago
  Today I'd consider going with a service, but first I'd see how https://github.com/LearnBoost/websocket.io https://github.com/LearnBoost/websocket.io looks. Most of our problems have been with abstractions in the socket.io client and scaling issues with server process chatter. The chatter shouldn't be necessary with websockets-only.
  • Rauchg 15y ago
    With https://github.com/LearnBoost/engine.io https://github.com/LearnBoost/engine.io the abstractions are greatly simplified, which is what I'm announcing today. The socket.io codebase has been shrunk dramatically, and it's as a result easier to scale/maintain.
    • deleted 15y ago
      [deleted]
    • dodger 15y ago
      That's great!