What you see above is a multiplayer version of the classic Snake game with a twist: whenever possible, it will automatically establish a peer-to-peer connection with your opponent. Today we’re very happy to introduce Socket.IO P2P, the easiest way to establish a bidirectional events channel between two peers with a server fallback to provide maximum reliability. Let’s look at the API and build a l
Server Socket.IO 1.3.0 is out with lots of fixes, in addition to stability and performance improvements. You can also now configure the clients with custom SSL and reconnection backoff parameters. Fix tests on Node v0.11 (dba462) [rauchg] Fixed socket.io test runs on windows (19c442) [rauchg] null and undefined origins trigger the origins callback properly with origin value * (GH#1936) [drewblaisd
Socket.IO 1.2.0 is now live with important bug fixes and a few API updates. We couldn’t have made this happen without the help of old and new contributors. A big hand to everyone who participated in the making of this release. Thank you! Below you can find more details on the changes and some code examples. Server Fixed the npm main property in the chat example (GH#1766) [BrianGeppert] Some gramma
Today we pushed version 1.1.0 of Socket.IO with a lots of bug fixes and some new additions. This release comes thanks to the work of more than 20 contributors. Server hasBin no longer iterates over object prototypes (GH#1645) [kevin-roark] Enhanced font styles in the chat example app (GH1653) [acusti] Fixed etag header in server socket.io.js (GH#1655) [ysmood] Fixed repo url in package.json (GH#16
The first version of Socket.IO was created shortly after Node.JS made its first appearance. I had been looking for a framework that easily enabled me to push data from a server to a client for a long time, and even had tried other approaches to server-side JavaScript. At the time, the main focus was on an interface equivalent to the upcoming WebSocket API that was in the process of standardization
Socket.IOBidirectional and low-latency communication for every platform PerformantIn most cases, the connection will be established with WebSocket, providing a low-overhead communication channel between the server and the client. ReliableRest assured! In case the WebSocket connection is not possible, it will fall back to HTTP long-polling. And if the connection is lost, the client will automatical
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く