实时应用程序：Socket.io 与 Pusherapp
What are the factors you would consider when choosing between Socket.io and Pusherapp? Important considerations include: integration with existing systems like rails/django, ease of setup, ease of development.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
有一些差异化因素，这些是：
Websocket 基本上有几种不同的用例，目前没有托管解决方案可以为您提供其中两种功能。我能想到的当前用例是：
--[ WebSocket ]->客户端<-[ WebSocket ]--客户端<-[ WebSocket ]->客户端像 PusherApp 这样的服务针对第一个用例，因为支持另外两个选项带有托管服务。 （请阅读：虽然这很困难，但有点不切实际，并且无法让您充分享受使用 websockets 的好处。）
There are a few differentiating factors, these are:
There's basically a few different use-cases for websockets, and at present no hosted solution can offer you two of those things. The current use cases I can think of are:
--[ WebSocket ]->Clients<-[ WebSocket ]--Clients<-[ WebSocket ]->ClientsServices like PusherApp target the first use-case, as it's fairly difficult to support the other two options with a hosted service. (Read: while it's difficult, it's just a bit impractical and doesn't give you the full benefits of using websockets.)