4 ms·
This isn’t a problem with HTTP/2. You can have as many SSE connections as you want across as many tabs as the user wants to use. Browsers multiplex the streams
by coder543 5y ago
This isn’t a problem with HTTP/2. You can have as many SSE connections as you want across as many tabs as the user wants to use. Browsers multiplex the streams over a handful of shared HTTP/2 connections.
If you’re still using HTTP/1.1, then yes, this would be a problem.
- leeoniya 5y agohmmm, you might be right. i wonder what steered me away. maybe each SSE response re-sends headers, which can be larger than the message itself? maybe it was inability to do broadcast to multiple open sse sockets from nodejs. i should revisit. https://medium.com/blogging-greymatter-io/server-sent-events-http-2-and-envoy-6927c70368bb https://medium.com/blogging-greymatter-io/server-sent-events...
- xg15 5y ago> maybe each SSE response re-sends headers, which can be larger than the message itself? That's (long) polling, not SSE. The only overhead for SSE are the "data", "event", etc pseudo header names and possibly some chunked-encoding markers. Both are tiny though.