Message processed 60 seconds after receive in edge

[tejoe]

Whenever a message needs to be split into multiple tcp packets, it will not be handled correctly in edge browser

After the first tcp packet is received the ajaxRequest.onreadystatechange function is called and correctly detects (Trackmessagesize), that the message is incomplete. The partial message is stored for later processing.

After the second/last tcp packet is received, the ajax request is updated (responseText), but the onreadystatechange function is not called. So the update is pending in the browser memory.

Only after the next update is received, the previous message will be processed. This is most likely after 60 seconds, which is the default heartbeatinterval.

All TCP packets are usually received within the same millisecond (according to wireshark). In other browsers it look like the onreadystatechange method is called after receiving the last packet. In Edge it is after the first packet

Environment Infos:
Client Version atmosphere-javascript-2.3.5
Server Version atmosphere-runtime-2.4.13
Transport: streaming