HTML and CSS Reference
The WebSocket protocol
TheWebSocket protocol redefines full-duplex communication fromthegroundup.Ac-
tually, WebSockets, along with WebWorkers, take a really enormous step in bringing
desktop-rich functionality to web browsers. Concurrency and multi-threading did not
truly exist in the postback world. They were emulated in a rather restrictive manner.
HTTP protocol requires its own schemas (http and https). So does the WebSocket
protocol. Here is a typical WebSocket URL example:
The first thing to notice is the ws prefix. This is pretty normal, as we need a new URL
schema for the new protocol. wss is supported as well and is the WebSocket equival-
ent to https for secure connections (SSL). The rest of the URL is similar to the plain
old HTTP URLs and is illustrated in the following image.
The following image shows the WebSocket URL in tokens:
For the time being, the latest specification of the WebSocket protocol is RFC 6455
and it's a blessing that the latest versions of every modern web browser support it.
More specifically, the RFC 6455 is supported in the following browsers:
• Internet Explorer 10+
• Mozilla Firefox 11+
• Google Chrome 16+
• Safari 6+
• Opera 12+