When sending buffered messages, only some of them are received by the server.
Socket.io buffers up messages as such:
It seems like only Message0 would be received here. I'm trying to confirm this atm.
That sounds funny.
The implementation should stop handling them when the length is right and return.
I can think of a few reasons:
It sounds likely it's number 1. Is this some part of the standard socket.io protocol that you should be able to just append messages to each other?
After a discussion, we've decided it is likely option no.1 that happens, especially with long polling calls that might buffer them up.
While we would probably need a test case to document everything, I'll just change the parser to return a list of messages if more than one exists.
Seeing the following: https://github.com/yrashk/socket.io-erlang/blob/master/src/socketio_transport_htmlfile.erl#L105
because we use gen_event to handle everything, I should be able to change the bits of code similar to the one above for something that just sends many notices. No messages should be lost after that.
This is fixed in 16815ab
Note that it is assumed that the first message of the string is the first one received.