A session represents a single counterparty, but it isn't exactly an
abstraction for a connection in the networking sense of the word. A session
can exist without a connection, and multiple connections can come and go
throughout the lifetime of a session.
I'm not sure about how you want to go about destroying a socket connection.
If you use the Session::logout method, the connection will be closed (either
through the normal logout procedure, or forcefully if necessary).
Session::logon will then establish a new connection.
--oren
----- Original Message -----
From: "VP Marketing IT Asset Enterprise Technologies" <ass...@gm...>
To: <qui...@li...>
Sent: Sunday, May 08, 2005 6:11 PM
Subject: [Quickfix-developers] Question about quickfix Session object
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
Hi
From http://www.quickfixengine.org/quickfix/doc/html/application.html
I read that Session object once created stays for the duration of the
application.
If there is a need to detroy and recreate the Session object is it possible?
Is the Session object an abstraction for connection with a Single
counterparty
or multiple counterparties?
Besides sending login-logout-login cycles, it is possible to destroy the
communication abstraction socket and recreate a socket.
I would appreciate if someone can provide some clarification.
Thank you
--
Raman
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id281&op=ick
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
|
