|
4.0 Session
< Previous Next >
re: Sequence Number reset after logon
Bob Lamoureux / Bridge Information Systems
26 Feb 1999 7:38AM ETThere are only two possibilities for A.
SOLUTION #1
Since A has only requested 1-7, A *MUST* hold on to 8 and insert it back into the message stream once 1-7 have been retransmitted and received. Party B must respond with a SeqReset to MSG 9 because that is where B is currently at after all admin messages have been taken into account.
SOLUTION #2
Party A accepts the LOGON, but asks for 1-8 in the ResendReq. This will effectively place message number 8 back on the end of any retransmission stream so that <A> doesn't have to do any compicated queueing/insertions. When B responds with SeqReset to 9, all is back in sync
- Bob Lamoureux
> Consider the following FIX session:
>
> PartyA>
> Sends Logon, MsgSeqNum = 8
>
> PartyB>
> (expected MsgSeqNum=1)
> Sends Logon
> Sends ResendRequest, BeginSeqNo = 1, EndSeqNo=7
>
> PartyA>
> (messages 1-7 were admin messages)
> Sends SequenceReset-GapFill, MsgSeqNo=1, NewSeqNum=8, PossDupFlag=Y
>
>
>
> Is this correct? Should PartyA send 8 as the NewSeqNum and duplicate the sequence number used for the logon message with the next message? Or should PartyA send NewSeqNum = 9?
>
> TIA
>
>
>
re: Sequence Number reset after logon
Bob Lamoureux / Bridge Information Systems 26 Feb 1999 7:38AM ET
|
