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

[Reggie D. <re...@me...>]

Sean,

I saw your posts from 4 months ago on the quickfix-developers list
regarding integrating QuickFIX socket connections into an async socket
loop.  I'm in the same situation now and I was hoping you could share
any progress you may have made over the last several months.

I'd like to write a single-threaded python application using "twisted"
which uses the QuickFIX python bindings to communicate with a FIX server
at one of our brokers.  I'm trying to get hold of the socket that the
SocketInitiator is using to use it in twisted's select loop and then
call the poll method of the Initiator when the select call indicates
that there is data ready on the socket.

Were you able to do anything like this with QuickFIX's python bindings?
Any guidance you can give would be appreciated.

Thanks,

-Reggie

On 22 Jun 2006, sea...@da... wrote:
> On 16 Jun 2006, at 9:40 PM, or...@qu... wrote:
>  > I don't know if I relish making these methods public in C++.  Swig  
>  > does allow you to pass macros into its preprocessor however, so we  
>  > can probably take advantage of that to allow the header to change  
>  > the protection to public when swig is processing the file.
>  
>  Actually even just making the methods public doesn't help. I  
>  discovered various other solvable issues but it came down to Swig  
>  needing to see the SocketConnector::Strategy declarations, and it  
>  doesn't support nested classes. At that point I gave up. I think I'll  
>  probably just make the FD available from SocketInitiator/ 
>  SocketAcceptor with an extra method and a custom patch.

-- 
Reggie Dugard <re...@me...>
Merfin, LLC