Viktor

Edge supports fetch API with streaming response body. Probably it will work faster. I have a code for this polyfill to use it. But didn't test it.

@bhaumikbarad , please try a new version which uses Fetch API as a transport in Edge

@adamtaylor13 , there is nothing in the source of the polyfill to drop large messages, it could be a bug or a browser bug in the underline browser APIs. What...

would be nice to debug this - to see if it is a browser bug or a bug in the library if it a browser bug - may be the...

@adamtaylor13 , do you have a stream to reproduce? (with CORS headers preferably)

@adamtaylor13 , it seems, there is nothing I can do - the polyfill uses a timer to check XMLHttpRequest#responseText. Try in Edge.

@varioous , it seems, your eventsource stream has a lot of whitespaces, such big respnose (like 1MB) are very slow in IE

```javascript function WebSocketTransport() { } WebSocketTransport.prototype.open = function (xhr, onStartCallback, onProgressCallback, onFinishCallback, url, withCredentials) { var ws = new WebSocket(url); ws.onopen = function () { onStartCallback(200, "OK", "text/event-stream", null); ws.send('data:...

@gautamrk1111, I don't know, can this be something related to new Angular? Shouldn't you use `observer.complete()` instead of `observer.unsubscribe()` in your example?

@helinfeng , you could write your own EventSource lib, may be you could use HttpURLConnection in separate Thread