[ajvpot]

I agree. Unfortunately you can only have 6 SSE streams per origin per browser instance, so you may be limited to 6 tabs without adding extra complexity on the client side.

https://crbug.com/275955

[TheP1000]

Is above still an issue with http2/3?

edit: From the article: To workaround the limitation you have to use HTTP/2 or HTTP/3 with which the browser will only open a single connection per domain and then use multiplexing to run all data through a single connection.

[gorjusborg]

No, if you can enable TLS and HTTP/2|3, you are only technically using a single browser connection, onto which multiple logical connections can be multiplexed.

I think the article calls this out. There is still a limit on the number of logical connections, but it's an order of magnitude larger.

[ravxx]

just use a service worker to share state, you would be much better off doing this anyways. saves a ton and is performant.

[simonw]

I think you need a SharedWorker for that rather than a service worker https://developer.mozilla.org/en-US/docs/Web/API/SharedWorke...

[paulddraper]

HTTP 2/3 doesn't have they limitation.

For HTTP 1, simply shard the domain.

[andrewmutz]

You can get around that limit using domain sharding, although it feels a bit hacky.

[xialvjun]

just one tab use SSE and others use storage event.

[nine_k]

Can the tabs share a background worker that would handle that?

[merb]

You can use https://www.npmjs.com/package/broadcast-channel which creates a tab leader, no need for a background worker

Edit: of course you could use: https://caniuse.com/sharedworkers but android does not support it. We migrated to the lib because safari took its time… so mobile was/is not a thing for us

[simonw]

Is that true if you are using HTTP/2?

[hobobaggins]

Yes, but the limit is different (usually much higher) and negotiated, up to maximum SETTINGS_MAX_CONCURRENT_STREAMS (which is fixed at 100 in Chrome, and apparently less in IOS/Safari.)

[cassepipe]

Nope. That's only a problem with HTTP/1.1