What about the javascript webSocket?

Not so long ago advised me on one public new tool ES6. Advised when I mentioned ajax. Very cool chip, judging by the description.
"It allows you to send any data to any domain, safely and almost without unnecessary network traffic." - application for https://learn.javascript.ru/websockets.
If anybody had any experience with this thing, and may be put into practice at the current time.
The fact that https://learn.javascript.ru/websockets you can deduct the vulnerability in the Protocol WSS too scary. In addition, the feature of ES6, I thought support would limp and it is more than 90%.

The tutorial is complex. A lot of conversion.
Did I understand correctly that this technology leaves no long queries in the address bar?
Your opinion: should I learn and use technology in commercial projects?
July 2nd 19 at 13:58
3 answers
July 2nd 19 at 14:00
Solution
Your opinion: should I learn and use technology in commercial projects?
Believe me, worth it. Some financial exchanges (as an example of a commercial project) actively using them. A web socket, it is essentially the most common socket, which is used about everywhere (in 99% of programs) work with network traffic, stranded on top of the web of reality (the HTTP Protocol).

Did I understand correctly that this technology leaves no long queries in the address bar?
This technology does nothing to the address bar and does with it not connected. It is a technology for transmitting data on a continuous basis in real time, for example, it is ideal for chats.

you can deduct the vulnerability in the system
If I remember correctly, the vulnerability is possible in the case of using a proxy ("counterfeit") and lack of encryption.

In addition, the feature of ES6, I thought support would limp and it is more than 90%.
Maybe I'm wrong, but I don't remember the connection between the RFC specification and ES6, besides, in my opinion, ES6 appeared late 2011. (which appeared in the RFC specification for web socket).

If anybody had any experience with this thing, and may be put into practice at the current time.
Was, I wrote a server and client in C/++, it's pretty much not noticed, the question of time and desire, that would be... detailed understanding of JS frameworks and libraries (e.g. Socket.IO), some actively use web sockets as a replacement for the long pools, flash sockets and so forth.

In the 2013-2014 year, support was still not very confident... in 2016 2017ΠΌ, I wouldn't be too worried about the users whose browsers web socket is not supported. Better suffers 3% of those who don't, 97% of those who could use them, but they are not used for the sake of those 3%...
July 2nd 19 at 14:02
First, a websocket is a communication Protocol implemented over http (wss - websocket secure work via https, respectively) and ECMAScript (the specification for JavaScript, ActionScript, and others like them) has no relation.
Secondly, the implementation of websocket client is included in the BOM the BOM (Browser Object Model), of the current browsers support almost everywhere, not only support IE9 and below (critical only if you can use this resource in the public sector) and Opera mini (mobile browser, which is the implementation of the standards stuck somewhere in the 90s)
Thirdly, websocket is radically different from ajax:
ajax allows you to make a classical http requests and works on the principle of request-response
websocket establishes a permanent connection, then the communication is in the form of sending of messages, though the messages can be send as server and client at any given time while the connection is established
Fourth, specifically in the implementation of websocket client in the browser has some limitations:
You cannot control headings when establishing a connection, the only way to transfer any data to the server at the time of establishing the connection is the url
Throughout the connection will be only one data exchange format, the choice is a string, ArrayBuffer, and Blob. If you need to send over the socket as binary data strings, the strings will be in the js packing in ArrayBuffer or Blob, respectively, to extract back when receiving messages
Fifth, although it would be better perhaps to zero, the server must be able to work on the Protocol websocket

In General, websocket can be used as an alternative to ajax, in SPA applications it can even give an increase of speed in communication with the server API in a kind of constant connections, but it has its troubles:
will need to implement a system request-reply (then you can take such a thing as socket.io and not steamed, though tormoznutaya, but comfortable + simulator on top of other transports for all sorts of IE9)
when sending big data, will have to bother broken down into parts, otherwise other messages will wait until the message is sent (it is not necessary to send more than 256KB at a time)
About the socket.io I heard. Used as a transport peredki data in nodejs applications.
Thank you very much, you gave me an idea about web sockets. Still can be used as an ajax alternative. Will unfold pleygraund and try to do the application perereca via a socket) - Arely.Casper commented on July 2nd 19 at 14:05
July 2nd 19 at 14:04
A thousand years have all used websocket: socket.io/docs

The main thing to understand that websocket don't need, why the need for Ajax, they have a different purpose.
The essence of websocket - continuously open connection with the server and ultra-fast exchanges of data.

The main consumers of this technology - chat rooms, games, services for simultaneous editing of documents, etc.
And unless websocket has anything relevant to ES6? - Arely.Casper commented on July 2nd 19 at 14:07
by the way Yes, in ES6 nothing to do with. - gustave_Kertzmann52 commented on July 2nd 19 at 14:10
we should not listen to assholes) WebSocket is a separate standard apart from ESMAScript - Rex.Bayer90 commented on July 2nd 19 at 14:13

Find more questions by tags JavaScript