3 ms·

I believe you have it essentially backward. Websockets consume a connection no matter what, as the protocol does not work with HTTP2 (there was an attempt, but

I believe you have it essentially backward. Websockets consume a connection no matter what, as the protocol does not work with HTTP2 (there was an attempt, but I believe it wasn't adopted and abandoned). The SSE requests do work with HTTP2, as do some other old methods like long polling. All the tabs will generally share one connection to that domain.

DaiPlusPlus 3y ago
> Websockets consume a connection no matter what, as the protocol does not work with HTTP2 (there was an attempt, but I believe it wasn't adopted and abandoned). Are you thinking of RFC 8441? https://www.rfc-editor.org/rfc/rfc8441 https://www.rfc-editor.org/rfc/rfc8441 If so, then it's already implemented by Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1434137 https://bugzilla.mozilla.org/show_bug.cgi?id=1434137 ...and by Chrome/Chromium since 91: https://chromestatus.com/feature/6251293127475200 https://chromestatus.com/feature/6251293127475200
- nitwit005 3y ago
  Thanks. Last time I checked I still saw them consuming connections, but I suppose that's probably the far end not supporting it.