Socket io why

I think the default socket. Am I wrong? I thought socket. Any documentation regarding Socket. Add a comment. Active Oldest Votes. Misconceptions There are few common misconceptions regarding WebSocket and Socket. IO: The first misconception is that using Socket. My experiment I wrote an npm module to demonstrate the difference between WebSocket and Socket. Server-side Compare the server-side example of using WebSocket and Socket.

IO Server Socket. IO server example using Express. IO Client Socket. Here are the results that I got: WebSocket Results 2 requests, 1. IO Results 6 requests, IO results that I got on localhost: Test yourself Quick start: Install: npm i -g websocket-vs-socket. To uninstall: Uninstall: npm rm -g websocket-vs-socket. Improve this answer. So basically what you are saying is that, websocket is better than socket. JackMoscovi I wouldn't say that WebSocket is necessarily better.

It all depends on the requirements. WebSocket's advantages are that it is a Web standard first under W3C and whatwg, now under IETF, with an RFC published 5 years ago , it is very lightweight because it is natively supported by the browsers, but the browser support while being good is not universal. IO supports more browsers and has more functionality, but also comes with some overhead. Sometimes one is better, sometimes the other. It's like choosing between querySelectorAll and jQuery - the answer is not always the same — rsp.

Great answer here!! It seems to me socket. See this great article too! Socket-io handles things like auto-reconnecting when interrupted which happens on mobile devices and I think there are security concerns around that which are handled for you?

Your plain WS examples, while functionally equivalent, do not have these properties. Very good comparison. However, it's worth noting that Socket. IO with Angular, Vue, React and others. Most importantly, you can disable Ajax long-polling and directly connect via WebSocket just like a raw WebSocket connection. In this way, you get everything except the kb library as equals.

Using WebSocket directly is painful unless you just need the bare minimum. Dropping rooms and access to the community IP is daunting for enterprise.

Show 2 more comments. This is a good read on both WebSockets and Socket. StackedQ 3, 1 1 gold badge 23 23 silver badges 38 38 bronze badges. Timothy Strimple Timothy Strimple IO is not build on top of WebSockets, it just uses this technology when it is available. So you have one more thing to do now:. Websockets should reconnect automatically in case of disconnection due to server failure or some other reason.

So now you added more code and tackled this problem too. Your boss appreciated your efforts, but now he tells you to add support for images blobs too. Not only this, you have to add chatroom for group chats, multiple endpoints so that you can connect multiple WebSockets. With some more code and hard work, you tackled these too. Now your WebSocket implementation looks something like this:. Guess what, this whole collection is actually what you call Socket.

Check out the image below just to make things crystal clear. IO is a JavaScript library for realtime web applications. It enables realtime, bi-directional communication between web clients and servers. IO primarily uses the WebSocket protocol with polling as a fallback option , while providing the same interface.

Note: Read that again and give extra attention to the text in bold. So far in index. During development, socket. That will install the module and add the dependency to package. Notice that I initialize a new instance of socket. Then I listen on the connection event for incoming sockets and log it to the console.

Now in index. We can also send Node. IO has played an important role in the popular adoption of Node. Version 1. IO has opened up some interesting possibilities for the Node. Peter has a great passion in software development particularly mobile web and android application development.

Discover Section's community-generated pool of resources from the next generation of engineers. The simple, flexible deployment options your customers expect with the low overhead your team craves. For Infrastructure Providers.