LearnBoost/socket.io — Issue #784: jsonp polling + IE7 + fast repetition of events
Author: samba2
Created: 2012-03-06 18:00:22+00:00
State: open

Hi,

I have a problem with sending events shortly after another to an IE 7 browser via
jsonp polling.

I switched on debug to give you some clues. The first "jsonppolling" action (value "12") is
received on the IE7 side. However, the program tries to send two further events shortly
after each other ( within milliseconds). Those two entries (values "13" and "14" ) do not appear
on the IE7 side.

The next events towards the browser are fired after a few seconds - this is working again. Only
quickly repeating events seem to have a problem with jsonp polling + IE7.

Is it critical in terms of reliability of data transport to fire multiple events after just some milliseconds break when using jsonp polling + IE7?

Beside this issue I am very satisfied with socket IO.

Any ideas? I'm using socket IO 0.8.7.

Many thanks for your support.

Maik

debug - setting request GET /socket.io/1/jsonp-polling/1603946467163662147?t=1331055340078&i=1
debug - setting poll timeout
debug - discarding transport
debug - cleared close timeout for client 1603946467163662147
debug - clearing poll timeout

// this one is received on the IE 7 side, value "12"
debug - jsonppolling writing io.j[1]("5:::{\"name\":\"eventLogEntry\",\"args\":[12]}");
debug - set close timeout for client 1603946467163662147
debug - setting request GET /socket.io/1/jsonp-polling/1603946467163662147?t=1331055353984&i=1
debug - setting poll timeout
debug - clearing poll timeout

// those two do not appear, value "13" and "14"
debug - jsonppolling writing io.j[1]("�40�5:::{\"name\":\"eventLogEntry\",\"args\":[13]}�40�5:::{\"name\":\"eventLogEntry\",\"args\":[14]}");
debug - set close timeout for client 1603946467163662147
debug - discarding transport
debug - cleared close timeout for client 1603946467163662147
debug - setting request GET /socket.io/1/jsonp-polling/1603946467163662147?t=1331055354031&i=1
debug - setting poll timeout
debug - discarding transport
debug - cleared close timeout for client 1603946467163662147
debug - fired close timeout for client 5670497771128082444