The web has always been a different playing field from the ground up, leaving no chance to interact with the client once the response is finished. This changed in the early 2000's with the rise of Ajax. Suddenly, the clients could request resources without requesting new HTML page. The next big problem that needed to be solved was the communication from the server to the client, which was done by introducing long polling when the client opened an HTTP request to which the server subsequently responded to, but never closed. This raised several issues but the biggest was the waste of resources by keeping the connection constantly alive. Servers with multiple concurrent users ran out of connections and the idea of keeping a connection open, even when there was no change, was a thorn in developers' flesh.

Some years later, in the early 2010's, RFC 6455 was adopted. Web Sockets, which is a part of the HTML 5 standard got introduced to the public but suffered from a slow implementation...