[This message was posted by Amit Gupta of <[email protected]> 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/345a7498 - PLEASE DO NOT REPLY BY MAIL.]
in my case, its number 2. John, Any suggestion/idea how to implement equivalent of the FIX MsgSeqNum+ResendRequest logic. Thanks > > Hi, I want to implement Resend logic in my application for the > > guranteed message delievery of the FIX message to the counterparties. > > Question is lets say my application creates and sends a message to my > > fix engine but somehow this message could not reach to fix engine and > > hence could not deleivered to counterparty, so how I could be sure > > enough that all message generated by my fix application sent to > > counterparty guranteed. > > > > I am looking for some suggestion/design pattern about how other > > people/companies implement this scenario. > > > > Thanks in Advance > > Two comments on this subject: > > 1. The more hops your data takes, the more latency and complexity. > Complexity because each hop needs some type of fault- > tolerance/recovery mechanism. Many people use "in-process" FIX > engines so there is no external hop from your application to the FIX > engine. Under that circumstance, there is no way for messages to be > out-of-sync with your FIX engine as they are bound together. > > 2. Just as FIX uses a bi-directional MsgSeqNum and ResendRequests, so > can you implement something similar. As Mahesh alludes, the > transport you use between your application and your FIX engine may > offer some type of message synchronization after an outage. It has > been my unfortunate experience that most 3rd party transport > software is big on promises of message resynchronization and short > on implementation of those promises. So you still might need the > equivalent of the FIX MsgSeqNum+ResendRequest logic. > > I hope this helps. > > JohnP [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 -~----------~----~----~----~------~----~------~--~---
