[This message was posted by Dennis Wiatzka of Nasdaq OMX <dennis.wiat...@nasdaqomx.com> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/4a1578fd - PLEASE DO NOT REPLY BY MAIL.]
> > Further, it will be a bad thing to allow the remote party to force a reset > > the session during an active business cycle. Other than the "...only keeps > > a message history of X messages" the scenarios are bugs which should be > > fixed rather than worked around this way. > > For the record, not only (software) bugs can cause the FIX session state to > become corrupt. A server may fail for a number of reasons. Even if you have > site failover and X number of hot standby servers, all these might fail. > > This proposal is about how to recover from a failure if it happens, instead > of saying that errors never happen. Kindly see this link for my reply. http://fixprotocol.org/discuss/read/b7a67693 [You can unsubscribe from this discussion group by sending a message to mailto:unsubscribe+100932...@fixprotocol.org] -- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to fix-proto...@googlegroups.com. To unsubscribe from this group, send email to fix-protocol+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
