3 ms·
Not quite. With requests over HTTP, there's an overhead for every single request. For websockets, you make one fat handshake/upgrade request to start with, and
by dynamite-ready 6y ago
Not quite. With requests over HTTP, there's an overhead for every single request. For websockets, you make one fat handshake/upgrade request to start with, and then all successive "requests" (frames) have no headers. So depending on what you're doing, and how you do it, it can be more efficient.
- MaxBarraclough 6y ago> With requests over HTTP, there's an overhead for every single request. Doesn't this go away with HTTP/3 and wherever QUIC is used?