Re: [Quickfix-developers] QuickFIX Python and Twisted

[Robert P. <rob...@gm...>]

Makes sense. And since the point was to use an asynchronous threaded
package like twisted, these callbacks can be made to be non-blocking.

So these changes would need to be made in the quickfix.i code?

rob


On 11/15/06, Oren Miller <or...@qu...> wrote:
> The allow threads macros I believe were explicitly designed for
> blocking IO calls, you can read mode about it here: http://
> www.gmu.edu/mlnavbar/webdev/doc-python/api/threads.html
>
> I would think that an IO library like one that does database queries
> is most likely aware of this and will implement these macros.  As
> long as they do, it should not be a problem since we called the end
> macro, they would be able to call the begin macro, then the end
> macro, allowing us to call the begin macro again.
>
> --oren
>
> On Nov 15, 2006, at 3:01 PM, Robert Parrott wrote:
>
> > This sounds reasonable enough to me, but I'm not familiar with
> > python threading.
> >
> > What happens if the python callbacks are long running (i.e. SQL
> > query). Would it block the main quickfix loop in this case?
>
>