MaxWebsocketMessageSize is hard-coded

[hoytech]

If you want bigger inbound messages you need to bump this up in src/main/c/Connection.cpp (and maybe also ReadWriteBufferSize -- dunno I did both), and then recompile library.

[mattgodbolt]

Good point! (wow, how big are your messages!) We should make this configurable though :)

[hoytech]

Hehe usually a lot smaller but in one case about 500 bytes bigger than that limit, which is how I noticed this :)

Outbound messages are sometimes 1M pre-compression and no problems there, this only seems to affect in-bound.

[A-J-Bauer]

I also noticed this when trying to send a large text file.
For testing I changed ReadWriteBufferSize, MaxWebsocketMessageSize in Connection.cpp to 256 * 1024.

This works for Firefox. Chrome however seems to send chunks for large strings. Presumably setting FIN bit 1 for the first, FIN bit 0 for following and FIN bit 1 for the last one. This however is not supported in HybiPacketDecoder.cpp (Line 46).

[stazio]

What is the state of this? Seasocks hangs for that one connection for me if I try to send too big of a string.

[A-J-Bauer]

You can check out my Pull Request "Support for fragmented Messages" (which I couldn't get thru test insanity) and see if it works for you.