messageLength of next message is glued after current one in IE

[janbols]

I'm using ...

• atmosphere 1.0.0,
• IE9 and
• transport=streaming.

I have an atmosphereHandler with a TrackMessageSizeInterceptor, AtmosphereResourceLifecycleInterceptor and BroadcastOnPostAtmosphereInterceptor.

On IE, the onMessage callback receives messages where the length of the next message is concatenated with the current one.

Also, the first message is not the payload, but the messageLength.
F.e. the following resonsebody ...
2113|<!-- ---------------------------------------------------------------- http://github.com/Atmosphere
...

102|{"availability":"OFFLINE","timestamp":"2012-09-05T17:36:42.256","messageType":"ownAvailabilityUpdate"}

... is turned into 2 onMessage callbacks:
1: 102
2: {"availability":"OFFLINE","timestamp":"2012-09-05T17:36:42.256","messageType":"ownAvailabilityUpdate"}

When multiple messages arrive, the payload is split incorrect.
F.e. the following responsebody ...
2113|<!-- ---------------------------------------------------------------- http://github.com/Atmosphere
...

444|{....first message ...}99|{... second message ...}99|{ ... third message ...}

... is turned into the following onMessage callbacks:
1: 444
2: {....first message ...}99
3: {... second message ...}
4: 99
5: { ... third message ...}

Notice how the 2nd & 3rd message (which are much smaller) are split correctly.

I don't have the same issues in chrome or firefox.

[janbols]

When I add the MessageLengthInterceptor to the mix, an extra | is placed between the current message and the next messagelength. In this case, the parsing is better, but the messageLength is still passed to the onMessage callback as an incoming message. So in the above example, the following messages would be passed in the onMessage callback:
1: 444
2: {....first message ...}
3: 99
4: {... second message ...}
5: 99
6: { ... third message ...}

[jfarcand]

Fixed, download it from here and let me know

[janbols]

Fixed indeed ;-)