Socket.IO vs. Pusher vs. Pushpin

Where we have browser support (recent Chrome, Firefox, and Safari), we make a WebSocket connection so that the server can push changes made by other people down to browsers listening on the appropriate channels. We use a modified version* of the Socket.io client and server libraries that allows us to keep many thousands of open WebSockets on each of our servers at very little cost in terms of CPU or memory usage. So when anything happens to a board you’re watching, that action is published to our server processes and propagated to your watching browser with very minimal latency, usually well under a second.

websocket for realtime communication and map sync

We use socket.io to power Ayedeals business. More specifically for real time analytics.

To communicate between login server and voice / messaging server

Everything on Zube happens in real-time. We hooked Socket into all of our models.

We use socket.io to notify user when long running UI tasks finish.

Live chat server

Real time communication

Used Socket.IO for webRTC application testing.

Sockets used to send latest location.

Socket.io is used for async communication.

Used for sending real-time updates to connected browsers; to give real-time feedback about e.g. messages assigned to you, resolves in the inbox, etc.

Socket.io is used as our current multiplayer engine. The existing engine is very simplistic and only utilizes the websocket+http fallback transports and serves as a generic world/zone/screen grouping mechanism for displaying users to each other.

Socket.IO has a decent community footprint, including integrations with popular JS frameworks, and has fallbacks to maintain an app's services if websockets are not available for some reason. Websockets are an important factor in most of the web-facing apps I build, to provide asynchronous two-way communication between the app and whatever server or data source it is connected to.

I use Socket.IO because using HTTP requests for a real-time multiplayer game just blows! Even with websockets, I had to scrunch the data being transmitted down to a bare minimum, and do some cheap compression tricks so that I can send data in JSON format. Otherwise, I would have to resort to sending binary data. I may end up doing that anyway when the time comes that I need to scale.

How do I use it? Each client opens a socket connection at startup. The server keeps track of these connections, and sends each client the visible portion of the Playfield repeatedly. The clients render this information, while sending requests and commands to the server (join,turn,fire,thrust,bomb,viewport change,etc.) in response to the player's actions. The server uses that to make adjustments to the player's ship on the Playfield.

Socket.IO powered all of the real-time editing capabilities - high performance, easy-to-use, and awesome.

• 웹소켓 클라이언트 Socket.io 를 통해서 간단한 및 알람 기능을 등을 만듬

chat server
raspberry message server

Another one that we're not using, yet. But have realtime data updates within our applications and the central API will be a great bit of functionality that gives our clients more control and keep them informed of changes and updates in their stores, in real time.

No delays!

Socket.IO's websocket fallbacks allow Hndhld to provide an experience for everybody.

P2P signalling

Socket.IO is used for basic websocket capabilities. Used for simple chat applications, and features that require realtime interactions with servers or other clients.

Chat services

Push real-time updates

Pusher is used to send update notification whenever Lapzbot joins a server.

Our UI version allows people to collaborate on maps in real time. One user can build and annotate a map and another can see the results and collaborate in real time.