The WebSocket protocol enables full-duplex interaction between a web browser (or other client application) and a web server with lower overhead than half-duplex alternatives such as HTTP polling, facilitating real-time data transfer from and to the server. To achieve compatibility, the WebSocket handshake uses the HTTP Upgrade header to change from the HTTP protocol to the WebSocket protocol. Although they are different, RFC 6455 states that WebSocket "is designed to work over HTTP ports 443 and 80 as well as to support HTTP proxies and intermediaries", thus making it compatible with HTTP. Both protocols are located at layer 7 in the OSI model and depend on TCP at layer 4. WebSocket is distinct from the Hypertext Transfer Protocol (HTTP) used to serve most webpages. It is a living standard maintained by the WHATWG and a successor to The WebSocket API from the W3C. The current specification allowing web applications to use this protocol is known as WebSockets. The WebSocket protocol was standardized by the IETF as RFC 6455 in 2011. WebSocket is a computer communications protocol, providing simultaneous two-way communication channels over a single Transmission Control Protocol (TCP) connection. A diagram describing a connection using WebSocket
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |