[This message was posted by Mark Thomson of LC <[EMAIL PROTECTED]> to the "4.4 Changes" discussion forum at http://fixprotocol.org/discuss/17. You can reply to it on-line at http://fixprotocol.org/discuss/read/165740ed - PLEASE DO NOT REPLY BY MAIL.]
Is anyone able to provide some advice as to servicing a 24hr market. At present we are planning on ensuring our FIX implementation follows the 24hr sequence reset rules as specified in the FIX Spec Vol 2 Session Protocol section. In my case the client is the initiator and I am the acceptor. I have a few questions: 1. In the 24hr case, should NextExpectedMsgSeqNum be used to ensure there are no race conditions between when the recommended test request / heartbeat is sent and then the logon msg ( with ResetSeqNumFlag=Y ) is sent? 2. If we need to do some house keeping around the session reset ( e.g archive old orders, roll logs , clear some caches etc ), would it be ok to perform these tasks following the successful logon msg ( with ResetSeqNumFlag=Y ) from the client. 3. In fact in the 24hr environment, what is the recommended approach to handle session housekeeping ( We need to do this so will don't bloat out a system with large numbers of old orders living until the whole system does a weekly reset for example) Any comments appreciated? [You can unsubscribe from this discussion group by sending a message to mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
