News for hackers. Stuff that matters.

A comment on Migrating Millions of Concurrent WebSockets to Envoy. Parent comment

Re:Migrating Millions of Concurrent WebSockets to Envoy by Matthias247 on Wednesday March 17, 2021 @07:22PM (#26498027)
You could do that. But it would introduce a lot of head of line blocking on that connection. In return you Save a TLS handshake which might not be too important for long lived connections.

Plus it requires the backend to support that custom multiplexing layer.

[ Parent | on HN ]
Re:Migrating Millions of Concurrent WebSockets to Envoy by muxator on Wednesday March 17, 2021 @09:09PM (#26498753)
How so? Why there should be a head of line blocking? This would be a simple multiplexing of the payloads.
[ Parent | on HN ]
Re:Migrating Millions of Concurrent WebSockets to Envoy by Matthias247 on Thursday March 18, 2021 @12:38AM (#26499713)
If there on the other connection a lot of messages are exchanged (and a websocket frame could be gigabytes long according to the spec) the other stream would be blocked behind that.Of course that can be mitigated by using a non websocket framing, but that in the end reinvents yet another transport layer.
[ Parent | on HN ]