websocket service

other directly between the two.The key point is how to "shake hands", so long as we have done the handshake, then Webscoket technology can be used.The previous said WebSocket and HTTP have the intersection, or can say WebSocket with the help of HTTP is reflected here, you can see the red dots in the figure, respectively, is the WebSocket request head and the res

TCP/IP, WebSocket and MQTT According to the OSI network layering model, IP is the Network layer protocol, TCP is the Transport Layer protocol, and HTTP and Mqtt are the application layer protocols. Between the three, TCP is the protocol for HTTP and Mqtt at the bottom. Everyone is familiar with HTTP, here is a brief introduction to MQTT. The MQTT (message Queuing Telemetry Transport, Messaging queue telemetry transmission) is an Instant Messaging pro

(" Disconnected "); } function OnMessage (evt) { console.log (' Retrieved data from server: ' + evt.data)} function OnError (evt) { cons Ole.log (' Error occured: ' + evt.data); }An example of a typical WebSocket initiating request and getting a response looks like this:WebSocket Handshake Protocol (client-to-server)Service-to-client:http/1.1 101 WebSocket P

BackgroundPreviously, many websites used polling to implement push technology. Polling is at a specific time interval (for example, 1 seconds), the browser sends an HTTP request to the server, and the server returns the latest data to the browser. The disadvantage of polling is obvious, the browser needs to constantly make requests to the server, however, the header of the HTTP request is very long, and the actual transmission of data may be very small, resulting in a waste of bandwidth and serv

WebSocket SecurityThe WebSocket protocol is a young technology, and brings with it some risks. Decades of experience has taught the web community some best practices around HTTP security, but the security best practi Ces in the WebSocket world aren ' t firmly established, and continue to evolve. Nevertheless, some themes has emerged and they is described in this

Browser already supports the HTTP protocol, why develop a new websocket protocol? We know that the HTTP protocol is a one-way network protocol, and after the connection is established, it only allows Browser/ua (useragent) to send the requested resource to webserver, webserver to return the corresponding data. and webserver can not actively push data to Browser/ua, originally so design HTTP protocol also has reason, assuming webserver can actively pus

object, which is the address of the server that needs to be connected, as the HTTP protocol uses http://, the WebSocket protocol URL uses the ws://, and the other secure WebSocket protocol uses the wss://start. Ws.send ("Hello"); is used to send messages to the service side 2.ws.onopen = function () {Console.log ("open")}; The OnOpen event is triggered

[This article is original, if reproduced, please indicate the source http://blog.csdn.net/yl02520/article/] WebSocket protocol is a two-way communication protocol, which is based on TCP and transmits data via TCP as HTTP, but it differs from HTTP by two points: 1. WebSocket is a two-way communication protocol, after the establishment of the connection, the WebSocket