{{Quickfixn}} How to handle unexpected disconnects?

[Mike Gatny]

You could, but there is no need to check repeatedly -- you'll never receive
an OnLogon() for a connection that never gets established, so you'll know
there's a problem with that session.

p.s. If you want to know which sessions exist (connected or not), implement
the OnCreate() callback.
On Jan 22, 2014 11:15 AM, "Michael Groeger" <mikeonquickfix at gmail.com>
wrote:

> Dear Mike,
>
> thanks for your reply. And what will happen when a connection never gets
> established for example when the acceptor is not responding or accepting
> connections? Is it correct to say that the application can/should handle
> this by contineously testing SocketInitiator.IsLoggedOn()?
>
> Best regards,
> Michael
>
>
> 2014/1/22 Mike Gatny <mgatny at connamara.com>
>
>> You will get an OnLogout() in case of both expected and unexpected
>> disconnect.  This callback is usually used along with OnLogon() to keep
>> track of the connection, e.g. sending alerts into external tools.
>>
>> _______________________________________________
>> Quickfixn mailing list
>> Quickfixn at lists.quickfixn.com
>> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>>
>>
>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20140122/8ffa23b9/attachment-0002.htm>