The original goal description refers to WebSockets, which on an older
draft 1 mentioned that each frame "starts with a 0x00 byte and ends
with a 0xFF byte." This seems to be no longer true in the current
WebSockets RFC 2 but we still want to avoid making use of the 0xFF
byte to support a reliable and efficient message framing for other use
cases.
cowtowncoder
commented
3 years ago
The original goal description refers to WebSockets, which on an older draft 1 mentioned that each frame "starts with a 0x00 byte and ends with a 0xFF byte." This seems to be no longer true in the current WebSockets RFC 2 but we still want to avoid making use of the 0xFF byte to support a reliable and efficient message framing for other use cases.
Fixes: https://github.com/FasterXML/smile-format-specification/issues/13 Signed-off-by: Juan Cruz Viotti jv@jviotti.com