Re: [Quickfix-developers] SocketRecvFailed Event
Brought to you by:
orenmnero
From: Hei C. <str...@ya...> - 2013-05-08 17:10:12
|
1. If you use nonblocking socket class (aka SocketInitiator/SocketAcceptor), then your send call just puts your messages on a queue. 2. This can always happen because if another end unplugs the cable, the socket won't be shut down properly. That's why there is heartbeat in the protocol. But you can use the blocking socket class to reduce the likelihood that you get a success from sendToTarget but it is actually a failure. ________________________________ From: yan guan <gy1...@gm...> To: qui...@li... Sent: Wednesday, May 8, 2013 12:35 AM Subject: [Quickfix-developers] SocketRecvFailed Event Hello, I have a question about QuickFIX. 1. The moment before I call sendtoTarget() the network failed, but I can not get the Logout Event instantly. Also sendtoTarget() returns true, and in fact, the message hasn't been sent out. 2. Another situation is after sendtoTarget() successfully, the network failed. I design my project this way, wait a period of time for the asynchronous message return. What my difficulty is if timeout and Logout, I can not whether the message is sent out or not. Regards, Yan QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html QuickFIX Support: http://www.quickfixengine.org/services.html ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |