socket.io：好的部分和坏的部分
我最近发现了socket.io，它似乎非常适合我对多人游戏的需求。据我了解，它在客户端和服务器之间的通信中所起的作用与 jQuery 在客户端查询和动画中所起的作用相同。这大致正确吗？
官方网站信息丰富，我发现了一些博客文章，例如 这个，吹嘘它是多么很棒。然而，我发现没有维基百科文章描述它，没有新闻条目，没有学术研究等等。那么，它的受欢迎程度如何是吗？
有点令人惊讶的是，除了像这个。由于某种原因，我没有找到关于它有多快、它有多有缺陷、它有多完整等等的评论。
我会在深入学习技术之前想知道我正在做什么！
I have discovered socket.io recently, and it seems to fit perfectly my needs for a multiplayer game. From what I understand, it serves the same role for communications between client and server that jQuery does for client-side querying and animations. Is that roughly correct?
The official website is kind of informative, and I've found a few blog posts, such as this one, boasting how awesome it is. However, I've found no Wikipedia article describing it, no news items, no scholarly research, etc. So, how popular is it?
Somewhat surprising, I have not been able to people complaining about its bad parts, apart from (understandable) bugs like this. For some reason I haven't found comments about how fast it is, how buggy it is, how complete it is, etc.
I would like to know what I'm getting into before diving in and learning the technology!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
注意：我的观点有偏见，因为我在 Socket.IO 工作，
我们有 http://socket.io 站点和一些github 上的 wiki 页面 (https://github.com/learnboost/socket.io/wiki）。它不是分配信息，但足以让您开始。
我认为目前还没有那么多信息的主要原因是node 和socket.io 相对较年轻。但它在 Node.js 社区中确实很受欢迎，当你想要实时通信时，socket.io 通常是第一个向你推荐的模块。
根据 npm（节点包管理器）的统计，它非常受欢迎 http://search.npmjs.org/ 因为它位于最依赖的模块列表中。另外，如果您查看 github 上存储库的统计数据，您会发现它非常活跃且受到喜爱。服务器有超过 2000 多个观察者和 220 多个分叉。客户端有 1300 多个观察者和 110 多个分叉。谷歌群组已有 1350 名成员。因此，这对于单个 Node.js 模块来说还不错（如果我可以这么说的话）。
至于错误，我们在几个月前启动了对代码的完全重写，结合了我们在 Socket.IO 0.6 上获得的经验教训和反馈，因此存在一些泄漏和错误，但我们正在努力解决这些问题。我已经修复了大部分已知的内存泄漏，它们有望出现在 socket.io 0.7.8 / 0.8 中。
希望这有帮助 <3
Note: My opinion is biased because I work on Socket.IO
We have the http://socket.io site and some wiki pages on github (https://github.com/learnboost/socket.io/wiki). It's not allot of information, but enough to get your started.
I think the main reason why there isn't that much information yet is because node and socket.io are relatively young. But it's really populair in the node.js community, when you want realtime communication socket.io is usually the first module that is suggest to you.
According to the stats of npm (node package manager) it's quite populair http://search.npmjs.org/ as it's in the list of most depended on modules. Also if you checkout the stats on the repositories on github you can see that it's quite active and loved. The server has more than 2000+ watchers and 220+ forks. And the client 1300+ watchers and 110+ forks. The google groups has 1350 members already. So that is not to bad for one single node.js module (if i may say so).
As for the bugs, we have launched a complete rewrite of the code a couple of months ago, incorporating the lessons and feedback we had on Socket.IO 0.6, so there a few leaks and bugs but we are working on hard on resolving those. I have already fixed most of the known memory leaks and they should hopefully land in socket.io 0.7.8 / 0.8.
Hopes this helps <3