Sometimes when decoding we can determine the session, but then a field is badly formatted etc.
Sometimes when decoding we can determine the session, but then a field is badly formatted etc. ie we cannot even create the well formed FixMsg, so we need to reject the message
SfInitiator or SfAcceptor, impacts initial state for login sequence
The optional persisten store, and also a boolean indicating if the initial sequence numbers should be read in, or left at 1
The session ID - it MUST match exactly the header values they other end sends
A global scheduler
records today if there was a session yet or not, if not reset seq nums
If <1 ignored
If <1 ignored