Today were 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.
I'm really proud to announce the first release of the Socket.IO C++ Client on GitHub!
We are pleased to announce the immediate availability of the Socket.IO Swift Client! Youll now be able to write code that runs natively on iOS and OSX, while maintaining the simplicity and expressiveness of the JavaScript client!
Socket.IO 1.3.5 addresses a parser issue. Upgrade recommended. Completely backwards-compatible.
<script src="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.3.5/socket.io.min.js"></script>
Socket.IO 1.3.4 corrects the 1.3.3 build that included extra unused code.
<script src="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.3.4/socket.io.min.js"></script>
Socket.IO 1.3.3 is a backwards-compatible recommended upgrade for everyone.
It addresses a bug in the parser that could break the decoder with maliciously-crafted binary packets.
We now warn about errors in the console if you dont manually specify an error event handler for Socket objects on the server.
As usual, you can grab the latest client from the CDN!
<script src="https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.3.3/socket.io.min.js"></script>
In this tutorial well learn how to create a chat client that communicates with a Socket.IO Node.JS chat server, with our native Android Client! If you want to jump straight to the code, it's on GitHub. Otherwise, read on!
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.