[jzwinck]

Here is a good message framing protocol built on TCP: https://www.nasdaq.com/docs/SoupBinTCP%204.0.pdf

If you want large messages just redefine the length from 16 to 32 bits.

It's been used for millions of messages per day for 25 years and hasn't been changed in a long time.

Admittedly it isn't as common as TCP and that's a shame. But it's out there, it's public, it's minimal and it makes sense.

[eru]

> SoupBinTCP guarantees that the client receives each sequenced message generated by the server in the correct order, [...]

This protocol guarantees too much. It's still a stream.

[jzwinck]

You quoted the part about sequenced messages. Look at the part about unsequenced messages right after that. It has both.

[eru]

Thanks!