- changed status to resolved
Support serialization-less SessionInit/Response message decoding for future compatibility
Issue #17
resolved
Support should be added for decoding SessionInit/Response messages using a version that will not be written yet. This will allow the next major version to use the new format and be compatible with 1.7.
Comments (1)
-
reporter - Log in to comment
Decode support for SessionInit/Response message version 4
Only the read side of message version 4 is support (currently writing version 3) so that we can roll out version 4 in 1.8. Message version 4 for SessionInit/Response allows parsing without de-serializing with primitive encoding for VMIDs and length headers for connection args and reconnect tokens.
Fixes:
#17→ <<cset 29dd5becb875>>