[This message was posted by Pravin Pillai of <[email protected]> to the "4.2 Changes" discussion forum at http://fixprotocol.org/discuss/5. You can reply to it on-line at http://fixprotocol.org/discuss/read/1747641b - PLEASE DO NOT REPLY BY MAIL.]
Hi Changpeng, I think you misinterpreted Mahesh's response. He is not saying that there will be 2 sessions between the client and sell-side. He was saying that we need 2 FIX engines on the sell-side, one to handle communication with the client and one to handle communication with the exchange. That said, I do agree with John Peng that a single FIX engine at the sell-side should be able to handle both the communication channels. > One FIX engine to support the connection between client and sell-side. > Client always initiates the session by <LOGON> and Sell-side replys <- > LOGON>. After the session established, data flows in duplex mode. Tha > advantage is only one port used. If the session fail, no data to > transfer between both sides. If you have to sessions, and one of them is > not connected. What do you do? You can send order to trade, but no > report back for updating your order management system. > > Good luck, peng [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 -~----------~----~----~----~------~----~------~--~---
