{{Quickfixn}} engine stop/restart

[Phillip Wei]

The Start/Stop functions on things implementing IInitiator (of which SocketInitator implements through AbstractInitator) do what I think you want.

So after you’ve created the SocketInitiator, you call Start() to start, Stop() to stop ... and then can Start() again.  You will not “destroy” (in C#, dispose) the classes, but you will close the Socket.  If you don’t want the socket to close for some reason, you can re-implement the SocketInitator, though, I can’t imagine why this matters (or is a good idea).

Phil

From: quickfixn-bounces at lists.quickfixn.com [mailto:quickfixn-bounces at lists.quickfixn.com] On Behalf Of ligu
Sent: Wednesday, November 27, 2013 10:05 AM
To: quickfixn at lists.quickfixn.com
Subject: {{Quickfixn}} engine stop/restart

Hi,

is there a way to stop/restart the engine?

I mean, forcing the engine to logout, and later login again only if forcing it,
without destructing engine classes (application, socketinitiator).

Thanks,
   Laszlo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20131127/957e3ce8/attachment-0002.htm>