Error comes eventually after all the reconnects (~20min) before hitting that … though maybe that still isn’t good?
Probably not. It would be interesting to see if there are open file descriptors or something that start to build up.
The cool thing about server sent events is that they are just plain http requests, with a special content type set to text/event-stream. The server keeps the request open and continues to write to the response body using a simple text protocol, like this:
id: 1
data: hello
id: 2
data: world
The browser parses the response stream as it receives data from the server. The browser also automatically handles reconnects when the connection breaks. It is a really nice, simple protocol and api 
me too
Is there any useful information in the browser console? Also which browser are you using? If not Chrome, can you repeat the issue in Chrome?
In the meantime, I will look at the frontend code to see if there is any additional information I can add that might help with debugging.
There are two differences I can think of.
The first difference is that we bundle a polyfill with rc.5 primarily for internet explorer. I remember reading that the polyfill will override the default Firefox implementation which is only partially compliant with the specification. Maybe there is an issue with the polyfill?
The second is that the browser does not automatically reconnect under some circumstances, so I added code to augment this behavior and to automatically reconnect. It is possible that I did not implement this correctly, or maybe it is only working properly in Chrome.
Let me know which browser and perhaps that will help me reproduce. Thanks and sorry about this 