Hacker News Reader

No, the browser's HTTP connection limits still apply on HTTP2, each `EventSource` per tab counts against this limit of I think 6 (?) connections.

Websockets to my knowledge have no such limit because they are not HTTP requests.

View on HN

This is simply not true, it's negotiated between the client and server and defaults to 100 usually. 6 is the limit for http 1.1 not http/2.

Source: https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...

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.

> 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

If so, then it's already implemented by Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1434137

...and by Chrome/Chromium since 91: https://chromestatus.com/feature/6251293127475200

Thanks. Last time I checked I still saw them consuming connections, but I suppose that's probably the far end not supporting it.

Reply on news.ycombinator.com