Re: [Quickfix-developers] Integrate socket connections into application-wide async socket loop

[<or...@qu...>]

<DIV name="wmMessageComp">Well, since the SocketInitiator *is* a
SocketConnector::Strategy, I don't see any reason why you can't just
inherit from SocketInitiator and override onConnect, onData and
onDisconnect (they should probably move from private to
protected).&nbsp;&nbsp;the Swig wrappers&nbsp;should allow you to do
this no problem.&nbsp; Just remeber to call the&nbsp;base
method&nbsp;in your overrides.&nbsp; Make sure your event loop has a
timeout so you can call poll occasionally in order to process timeouts
and such.&nbsp; Timing out every second&nbsp;will work well for any
heartbeat interval.</DIV>
<DIV name="wmMessageComp">&nbsp;</DIV>
<DIV name="wmMessageComp">--oren</DIV>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT:
blue 2px solid" name="wmMessageComp">I guess in C++ I would subclass
the strategy as that owns the FDs, &nbsp;<BR>and then use a replacement
SocketInitiator that subclasses my &nbsp;<BR>customized strategy and
Initiator. Would that be the right way to go? &nbsp;<BR>Could I
actually do this all successfully in pure Python? If I can,
&nbsp;<BR>then I'll still have to rewrite SocketInitiator in Python
right?<BR></BLOCKQUOTE>