Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EventSource vs maximum number of HTTP connections per domain #382

Open
shamrin opened this issue Jan 28, 2016 · 0 comments
Open

EventSource vs maximum number of HTTP connections per domain #382

shamrin opened this issue Jan 28, 2016 · 0 comments

Comments

@shamrin
Copy link

shamrin commented Jan 28, 2016

EventSource, currently listed as "use, with fallback", has a hard-to-debug problem when using it in real life. Every additional EventSource connection counts against maximum number of HTTP connections per domain. This limit is usually very low. In contrast, WebSocket connection limit is usually not a problem. In my experience this problem could be hard to debug, because you would only notice it when you have a couple of tabs opened. After a certain limit, additional tabs would fail to work properly.

I was personally burned by this problem, when I've decided to ignore WebSockets and use only EventSource in a project. And I'm not the only one. FastMail had to implement inter-tab communication via localStorage to fix this problem. And their solution doesn't work in all cases. E.g. Safari in private mode doesn't allow localStorage.

What do you think? Does it make sense to warn about this problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants