Imported from previous forum
[ original email was from Natan Kugel - nkugel@espeed.com ]
Dear all:
This is related to tag 141 available in 4.3.
If the client drives sequence number reset, connects as well as logs on using sequence number 1 | tag 141=Y, the server will reset sequence numbers and will replu with logon | tag 141=Y.
If the server drives sequence number reset, is the only option (A) for the server to wait for the client to connect and log on with next sequence number (tag 141=N or absent), exchange the heart beats and send another logon seq. num 1 | tag 141=Y and wait for response from client?
Could the server, (B) replay to logon seq num = next | tag 141=N or absent with logon seq num 1 | tag 141=Y.
This would reduce time it takes for resynch and sequence number reset, if driven by server.
It seems option A follows FIX specs verbatim.
Question 1) Is option B a valid option?
2) If Yes, then the server should not generate resend requests as result of client’s first logon (prior to sequence number reset).
3) If Yes, the client then would need to send another logon with sequence number 1 | tag 141=Y
Please confirm the understanding.