Re: [whatwg/fetch] Refactoring WebSocket connections (#1243)

Chrome uses a separate pseudo-socket pool for non-H2/H3 WebSocket connections, which enforces WebSocket connection limits (And uses slightly different connection attempt ordering rules in the case of multiple IP addresses for a single DNS lookup, since WebSocket enforces limits on a per-IP-address basis, I believe).  Chrome never repurposes an HTTP/1.x socket for use with WebSockets.

For H2 WebSocket connections, it looks for an existing H2 connection that supports WebSockets to the corresponding origin.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1243#issuecomment-852239983