Socket.io: Good Parts and Bad Parts

Question

I recently discovered socket.io and it seems to fit my needs for a multiplayer game. From what I understand, it performs the same role for communication between client and server as jQuery does for client requests and animations. Is it correct?

The official site is informative, and I found several blog posts such as this one , showing off being awesome . However, I found a Wikipedia article , without news , no scientific research , etc. So how popular is this?

It is somewhat surprising that I could not complain about its bad parts , except for (understandable) errors, such as. For some reason, I did not find comments about how fast , how buggy , how complete , etc.

I would like to know what I'm getting into before diving and learning technology!

Answer 1

Note. My opinion is biased because I'm working on Socket.IO

We have a http://socket.io website and some wiki pages on github ( https://github.com/learnboost/socket.io/wiki ). It does not contain information, but enough to get started.

I think the main reason that so far is not a lot of information is because node and socket.io are relatively young. But this is really a populair in the node.js community, when you want socket.io real-time communication is usually the first module that offers you.

According to the statistics of npm (node ​​package manager) it is quite popular http://search.npmjs.org/ , because it is in the list of the most dependent on modules. Also, if you check the statistics on repositories on github, you can see that it is quite active and loved. The server has over 2000+ observers and 220+ forks. And the client has 1300+ observers and 110+ forks. There are already 1350 members in google groups. So this is not bad for a single node.js module (if I may say so).

As for the errors, we launched a complete rewrite of the code a couple of months ago, taking into account the lessons and feedback that we had on Socket.io 0.6, so there are a few leaks and errors, but we are working hard to resolve them. I have already fixed most of the known memory leaks, and they hopefully land in socket.io 0.7.8 / 0.8.

Hope this helps <3