[Quickfix-developers] RE: Request resend

[Fad <s.f...@gm...>]

Dave Linaker wrote:
> 
>  
> If you are doing this then I would expect you to see the following from
> CLIENT_ALL1's perspective:
>  
> - CLIENT_ALL1 receives MsgSeqNum 81768 (Next expected seq num changes to
> 81769)
> - CLIENT_ALL1 receives MsgSeqNum 81769 (Next expected seq num changes to
> 81770)
> - CLIENT_ALL1 receives MsgSeqNum 81770 (Next expected seq num changes to
> 81771)
> - CLIENT_ALL1 manually sends ResendRequest 7=81768|16=81770
> - CLIENT_ALL1 receives MsgSeqNum 81768 (igored because Next expected seq
> num changes to 81771)
> - CLIENT_ALL1 receives MsgSeqNum 81769 (igored because Next expected seq
> num changes to 81771)
> - CLIENT_ALL1 receives MsgSeqNum 81770 (igored because Next expected seq
> num changes to 81771)
>  
> 

It is not true, infact the client after send "ResendRequest" recive a
SeqReset-GapFill with PossDupFlag set to "Y". It's ok, because the
client-server session are syncronized.

But if the client-server session are not syncronized, the quickFix engine
instead of resend the 'lost message' sends however the SeqReset-GapFill
message with PossDupFlag set to "Y" (in the logs file thera are the message
that the server should resend).

Stefano.

--
View this message in context: http://www.nabble.com/Request-resend-t1430121.html#a3868937
Sent from the QuickFIX - Dev forum at Nabble.com.