We have tests (unit and the chat app) that use "normal" strings as the data passed to SocketIO. But it seems reasonable that SocketIO can accept unrestricted binary data.
We should determine what data SocketIO accepts, then make sure to cover those scenarios in the unit tests. For example:
Unicode data (including Chinese Ext-B characters)
Binary data (however that might be represented)
Strings that include characters that are special to the serialization formats (like JSON characters that get escaped, XML escape characters, characters that are not valid in XML (0xFFFE, 0x05))
We have tests (unit and the chat app) that use "normal" strings as the data passed to SocketIO. But it seems reasonable that SocketIO can accept unrestricted binary data.
We should determine what data SocketIO accepts, then make sure to cover those scenarios in the unit tests. For example: