Socket.IO is made up of two primary sections. A client library that runs in the user's browser, and a server-side counterpart, running on top of a Node.js server.
These two work via HTTP sockets and allow seamless data exchange between the user's browser and a server-side application, working in near real-time and providing immediate updates to both the local user data and the server's backend.
The main transport medium is WebSockets with an immediate fallback to AJAX polling, supporting features like mult-socket broadcast, async I/O, and client-based data storage.
Many frameworks already support Socket.IO and a few of them made it the central point of their core code, like Express and Koa.
In the industry today, Socket.IO is the go-to solution whenever needing real-time capabilities added to an app, mainly due to its broad ranging support of most Web browsers, and its well documented codebase.
Socket.IO supported transports:
WebSocket
Adobe Flash Socket
AJAX long polling
AJAX multi-part streaming
Forever iframe
JSONP polling
What is new in this release:
- Added test to check that empty rooms are autopruned
- Added Server#origins(v:Function) description for dynamic CORS
- Added test coverage for Server#origins(function) for dynamic CORS
- Added optional Server#origins(function) for dynamic CORS
- Fixed usage example for Server#close
What is new in version 1.3.7:
- Added test to check that empty rooms are autopruned
- Added Server#origins(v:Function) description for dynamic CORS
- Added test coverage for Server#origins(function) for dynamic CORS
- Added optional Server#origins(function) for dynamic CORS
- Fixed usage example for Server#close
What is new in version 1.3.6:
- Added test to check that empty rooms are autopruned
- Added Server#origins(v:Function) description for dynamic CORS
- Added test coverage for Server#origins(function) for dynamic CORS
- Added optional Server#origins(function) for dynamic CORS
- Fixed usage example for Server#close
What is new in version 1.3.5:
- Added test to check that empty rooms are autopruned
- Added Server#origins(v:Function) description for dynamic CORS
- Added test coverage for Server#origins(function) for dynamic CORS
- Added optional Server#origins(function) for dynamic CORS
- Fixed usage example for Server#close
What is new in version 1.0.2:
- Fix:
- socket.io-parser for Windows.
Requirements:
- Node.js
- JavaScript enabled on client side
Comments not found