How do you inspect websocket traffic with Chrome Developer Tools? [duplicate]

You need to reload the page with the network tab open and filter by type ‘ws’. This will show you a connection being made with a websocket. You can then click on the connection to show the traffic being sent back and forth with the server https://developers.google.com/web/tools/chrome-devtools/network-performance/reference#frames

Maximum concurrent Socket.IO connections

This article may help you along the way: http://drewww.github.io/socket.io-benchmarking/ I wondered the same question, so I ended up writing a small test (using XHR-polling) to see when the connections started to fail (or fall behind). I found (in my case) that the sockets started acting up at around 1400-1800 concurrent connections. This is a short … Read more

WebRTC vs Websockets: If WebRTC can do Video, Audio, and Data, why do I need Websockets? [closed]

WebRTC is designed for high-performance, high quality communication of video, audio and arbitrary data. In other words, for apps exactly like what you describe. WebRTC apps need a service via which they can exchange network and media metadata, a process known as signaling. However, once signaling has taken place, video/audio/data is streamed directly between clients, … Read more

Does HTTP/2 make websockets obsolete?

After just getting finished reading RFC 7540, HTTP/2 does obsolete websockets for all use cases except for pushing binary data from the server to a JS webclient. HTTP/2 fully supports binary bidi streaming (read on), but browser JS doesn’t have an API for consuming binary data frames and AFAIK such an API is not planned. … Read more