Re: [fetch] Introduce "connection pool" and a concept of a "connection" (#114)

Yeah, things get messy when you consider H/2 pooling (cross-origin), and also multi-profile (I read "User-agent-wide" to be ambiguous)

That said, that's extreme spec pedantry, and I think other than those pedantic nits which don't meaningfully alter things, yes, that sounds like the right idea.

re: WebSockets: The story on Chrome is complex, and the code itself is quite difficult to read. It's "supposed" to be that WebSocket connections can re-use connections from the underlying pools (e.g. the TCP pool that feeds into the TLS pool that is then used for WSS), but that those connections don't count against things like connection limits (since part of the point of WS[S] was to avoid HTTP/1.1 connection limits). AIUI, if we try a WS handshake and it fails to go through the Upgrade path, we'll still let that HTTP/1.1 connection hang out in the pool if it was Keep-Alive. But if they completed the Upgrade, they'll never re-enter the pool. But honestly, I can't give you a clear answer about what is supposed to happen or what will happen, so deferring that sounds good :)

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/114#issuecomment-143500095