最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

javascript - Real time apps: Socket.io vs Pusherapp - Stack Overflow

programmeradmin1浏览0评论

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.

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.

Share Improve this question edited Nov 1, 2011 at 23:38 John Bachir 22.8k30 gold badges160 silver badges238 bronze badges asked Oct 6, 2010 at 20:01 meowmeow 28.2k36 gold badges121 silver badges178 bronze badges
Add a ment  | 

1 Answer 1

Reset to default 9

There are a few differentiating factors, these are:

  1. Do you want to manage the scaling and hosting of your realtime infrastructure?
  2. Do you want to receive data from your clients in realtime?
  3. Do you want to be able to interact with the data between clients?

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:

  1. Server --[ WebSocket ]-> Clients
  2. Server <-[ WebSocket ]-- Clients
  3. Server <-[ WebSocket ]-> Clients

Services 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.)

发布评论

评论列表(0)

  1. 暂无评论