Re: [Quickfix-developers] How to check for dropped socket
Brought to you by:
orenmnero
|
From: Alvin W. <AW...@FF...> - 2005-06-23 19:08:38
|
A related question:
It seems that I can use the static method Session.sendToTarget(Message, SessionID) successfully even when the corresponding session is not logged on. (I am
not sure if the counterparty really receives the message in this case)
thanks
Alvin
Francis Gingras <fr...@at...>
Sent by: qui...@li...
06/23/2005 02:58 PM
To: qui...@li...
cc:
bcc:
Subject: [Quickfix-developers] How to check for dropped socket
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
QuickFIX Support: http://www.quickfixengine.org/services.html
I am using the initiator and I'd like to know how I can check if the
socket
was dropped. (i.e. if the connection was shut down by the acceptor side)
I figure I can use these properties but I'm not 100% sure what they mean:
session.isEnabled()
If the session exists, how can it not be enabled?
session.isLoggedOn()
socket.isLoggedOn()
Are they always the same and do they mean the same thing?
Thanks,
Francis Gingras
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
**********************************************************************
This e-mail message is intended solely for the use of the addressee.
The message may contain information that is privileged and confidential.
Disclosure to anyone other than the intended recipient is
prohibited. If you are not the intended recipient, please do not
disseminate, distribute or copy this communication, by e-mail or
otherwise. Instead, please notify us immediately by return e-mail
(including the original message with your reply) and then delete
and discard all copies of the message. We have taken precautions to
minimize the risk of transmitting software viruses but nevertheless
advise you to carry out your own virus checks on any attachment to
this message. We accept no liability for any loss or damage caused
by software viruses.
**********************************************************************
|