Conversation
Clarify that `msgSerial` should reset to `0` on clean connection attempts, including reconnects after `SUSPENDED`.
SimonWoolf
left a comment
There was a problem hiding this comment.
This sort of requirement does not belong in TRxx, which is just listing the fields of a ProtocolMessage. Should be in the RTN section.
RTN15g already states:
** @(RTN15g)@ Connection state is only maintained server-side for a brief period, given by the @connectionStateTtl@ in the @connectionDetails@, see "CD2f":#CD2f. If a client has been disconnected for longer than the @connectionStateTtl@, it should not attempt to resume. Instead, it should clear the local connection state, and any connection attempts should be made as for a fresh connection
"clear the local connection state" technically does already imply setting the msgSerial to 0. But it's implicit; worth rewording that item to make it more explicit exactly what should be cleared (connectionId, connectionKey, msgSerial) if people are confused.
Clarify that
msgSerialshould reset to0on clean connection attempts, including reconnects afterSUSPENDED.There is nothing in the spec about going back from
SUSPENDED, and we have different implementation at least in js and java. js resetsmsgSerialaftersuspended, java doesn't.msgSerialreset is mentioned in resume attempts and manualconnect()after terminal states.