[This message was posted by Mahesh Kumaraguru 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/03f389a0 - PLEASE DO NOT REPLY BY MAIL.]
If your Application is sending out FIX.4.4 messages to your FIX engine which sends FIX.X.Y messages to your counterparty, then I believe your application has an in-process FIX Engine because your application is producing FIX messages which is what FIX engines do. What do you gain by the extra FIX engine between your application's in-process FIX engine and the counterparty ? What prevents your application's in-process FIX engine from directly communicating with your counterparty ? > > Yes, I use FIX 4.4 as messaging protocol. > > So, as per your suggestion if i want to implement seq numbering and > resend request logic, any pointer where i can get this information? any > particular section in FIX spec which talks about this logic > implentation? > > Thanks a lot. > > > > So your Application and FIX Engine communicate thru Sockets. What is > > the messaging protocol on this socket connection ? > > > > If its FIX between your application and engine, then you would use the > > Sequence numbering and Resend request logic as provided by FIX. > > > > If its non-FIX, for example you write positional or delimited String > > which the FIX engine converts to FIX message, then as John has stated > > in this post below you would need to build Sequence numbering and > > Resend request logic in these Strings between application and Engine > > similar to FIX. > > > > > Mahesh, i did not get you exactly, but if your question is if my > > > applcation hosts my fix engine (i.e. in process) then it is not. I > > > communicate my fix engine through socket. > > > > > > Thanks, > > > > > > > is communication between the application and fix engine in FIX ? > > > > or is it a local method call or RMI or MQ etc ? > > > > > > > > > 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 [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 -~----------~----~----~----~------~----~------~--~---
