Why socket.io

Let me know if this was helpful. A javascript enthusiast and a creator who knows how to use keyboard, pen, pencil and gamepad to their fullest. Coding tutorials and news. The developer homepage gitconnected. Sign in. IO — What, Why and How? Shad Mirza Follow. Level Up Coding Coding tutorials and news. Level Up Coding Follow. Written by Shad Mirza Follow. More From Medium. Eke, Chinedu. Prototype Chaining in Javascript.

This is what Socket. And then a client can connect to multiple rooms simultaneously, disconnect them independently, and handle their events independently. Without this feature of Socket. There is often a lot more to making this work cleanly than you might think.

There are two important advantages to event encoding, one I think is less important, and the other is more important. The less important one is that when the protocol itself encodes the naming of events, libraries that implement the protocol can then understand more about your events, and provide features on top of this.

The JavaScript Socket. The reason why I think this is the less important advantage is because I think callbacks are a bad way to deal with streams of events communicated over the network. In those cases, you also often need higher level mechanisms like backpressure, delivery tracking, guarantees, and lifecycle management.

It allows the event name to be independent of the actual encoding mechanism, and this is of particular important for binary messages. You could encode it inside the JSON object, but that requires using base 64 and is inefficient. You could send it as a binary message, but then how do you attach metadata to it like what the name of the event is? As I said earlier, one of my values is reactive streaming, as this allows resilience properties such as backpressure and message guarantees to be implemented.

Callbacks offer no such guarantees. Of course, whether callbacks or streams are used to implement Socket. The implementation of Socket. The authors of Socket.

Nevertheless, the callback centric design of Socket. As a Socket. It can be invoked by the remote side, which will result in the callback on the local side being invoked with the arguments passed by the remote side. Acknowledgments are wrong for all the same reasons that Socket. Acknowledgments subvert back pressure and provide no guarantees with a stream you can have causal ordering and use that for tracking to implement at least once delivery guarantees, but acknowledgments have no such ordering and hence no such guarantees can be implemented.

The acknowledgments feature can be used to acknowledge that a message was received, but this requires the server to track what messages have been received. For up-to-date documentation, see the latest version 4. Version: 3. The Socket. IO codebase is split into two distinct layers: the low-level plumbing: what we call Engine. IO, the engine inside Socket. IO itself Engine. Most web developers nowadays want to develop real-time web applications or customize their existing applications to become real-time in order to satisfy their users needs appropriately.

This is where websockets play a major role. Websocket is a computer communication protocol that enables full-duplex communication between the client and server over a single TCP connection. Websocket protocol which is located at layer 7 of the OSI model enables interaction between a web browser or other client applications and a web server with lower overhead than half-duplex alternatives such as http polling hence promoting real-time data transfer between the two.

The project contained two parts before version 1. With the major release, transport handling has been moved to Engine. Apart from that, socket. Setting up socket.