There is currently only one subprotocol name (soap) registered as of February 2012.

The subprotocol names must be one of registered subprotocol names in IANA registry. Accepted subprotocol can be determined by accessing protocol property of WebSocket object. Each string should represent a subprotocol name and server accepts only one of passed subprotocols in the array. It can be a string or an array of strings. The second argument accepts optional subprotocols. Wss: for secure WebSocket connection the same way https: is used for secure HTTPĪttaching some event handlers immediately to the connection allows you to know when the connection is opened, received incoming messages, or there is an error. This is the new URL schema for WebSocket connections. Var connection = new WebSocket('ws:///echo', ) You open up a WebSocket connection simply by calling the WebSocket constructor: In plain words: There is an persistent connection between the client and the server and both parties can start sending data at any time. The WebSocket specification defines an API establishing 'socket' connections between a web browser and a server.

Introducing WebSocket: Bringing Sockets to the Web Think multiplayer first person shooter games in the browser or any other online game with a realtime component. However, all of these work-arounds share one problem: They carry the overhead of HTTP, which doesn't make them well suited for low latency applications. You use them every day in applications such as GMail chat. Long polling and the other techniques work quite well. Whenever the server actually has new data it sends the response (other techniques involve With long polling, the client opens an HTTP connection to the server which keeps it open until sending response. One of the most common hacks to create the illusion of a server initiated connection is called long polling. They go by names such as 'Push' or 'Comet'. Technologies that enable the server to send data to the client in the very moment when it knows that new data is available have been around for quite some time. Still, all HTTP communication was steered by the client, which required user interaction or periodic polling to load new data from the server. Around 2005, AJAX started to make the web feel more dynamic. A client loads up a web page and then nothing happens until the user clicks onto the next page. The web has been largely built around the so-called request/response paradigm of HTTP. The Problem: Low Latency Client-Server and Server-Client Connections

Android web server html5