Socket.IO

This article has multiple issues. Please help or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article relies too much on references to primary sources. Please improve this by adding secondary or tertiary sources. (January 2016) (Learn how and when to remove this template message) This article contains content that is written like an advertisement. Please help by removing promotional content and inappropriate external links, and by adding encyclopedic content written from a neutral point of view. (January 2016) (Learn how and when to remove this template message) This article may rely excessively on sources too closely associated with the subject, potentially preventing the article from being verifiable and neutral. Please help by replacing them with more appropriate citations to reliable, independent, third-party sources. (January 2016) (Learn how and when to remove this template message) This article needs additional citations for verification. Please help by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources:  –  ·  ·  · scholar · JSTOR (October 2013) (Learn how and when to remove this template message) (Learn how and when to remove this template message)

Socket.IO

Original author(s)	Guillermo Rauch
Developer(s)	Automattic
Stable release	4.0.0 / March 10, 2021 (2021-03-10)[1]
Repository	github.com/Automattic/socket.io
Written in	JavaScript
Operating system	Cross-platform
Type	Event-driven networking
License	MIT License[2]
Website	socket.io

Socket.IO is a JavaScript library for realtime web applications. It enables realtime, bi-directional communication between web clients and servers. It has two parts: a client-side library that runs in the browser, and a server-side library for Node.js. Both components have a nearly identical API. Like Node.js, it is event-driven.

Socket.IO primarily uses the WebSocket protocol with polling as a fallback option,^[3][4] while providing the same interface. Although it can be used as simply a wrapper for WebSocket, it provides many more features, including broadcasting to multiple sockets, storing data associated with each client, and asynchronous I/O.

It can be installed with the npm tool.^[5][6]

Overview[]

Socket.IO provides the ability to implement real-time analytics, binary streaming, instant messaging, and document collaboration.^[7] Notable users include Microsoft Office, Yammer, and Zendesk.^[8]

Socket.IO handles the connection transparently. It will automatically upgrade to WebSocket if possible. This requires the programmer to only have Socket.IO knowledge.

Socket.IO is not a WebSocket library with fallback options to other realtime protocols. It is a custom realtime transport protocol implementation on top of other realtime protocols. A Socket.IO implementing server cannot connect to a non-Socket.IO WebSocket client. A Socket.IO implementing client cannot talk to a non-Socket.IO WebSocket or Long Polling Comet server. Socket.IO requires using the Socket.IO libraries on both client and server side.

As of version 2.0, Socket.IO makes use of WebSockets as the underlying WebSocket library.^[9]

References[]

External links[]

• Official website
• socket.io on GitHub
• Socket.IO Tutorials

This Web-software-related article is a stub. You can help Wikipedia by .

• v
• t