{{Quickfixn}} Socket Deadlock Issue

[Matt Wood]

Grant,

Just for clarity, are you saying that the C++/java versions are using
a separate thread for processing?

On Fri, Jun 8, 2012 at 2:37 PM, Grant Birchmeier
<gbirchmeier at connamara.com> wrote:
> By the way, this isn't a new thing.  This same behavior is in the C++ and
> Java versions too.
>
>
> On Fri, Jun 8, 2012 at 1:33 PM, Manuel Lopez <lopez.post at gmail.com> wrote:
>>
>> To the extent that this would solve or ameliorate some of the issues, it
>> would be helpful if some application code along the lines suggested by
>> Thomas Tomiczek and others could be provided as part of the quickfixn
>> documentation.  It wouldn't be anyone's real app code, but a bare
>> bones example of the recommended pattern.  Thanks.  (fwiw I think the most
>> recent versions of c# have simplified the syntax for handling separate
>> threads.)
>> --Manuel
>>
>>
>>>
>>> The way I handle this is:
>>>
>>>
>>> *         Take incoming message
>>>
>>> *         Propagate to my own queue, then handle it from there.
>>>
>>>
>>> As a result, I am not even "cracking" messages in the receiving thread,
>>> but later in the processing handler. This one runs, as I said, in a
>>>  separate thread with an in memory queue ;)
>>>
>>> Yes, it COULD fill up, but that would require a large amount of messages
>>> ;)
>>>
>>> Regards
>>>
>>> Thomas
>>>
>>
>> _______________________________________________
>> Quickfixn mailing list
>> Quickfixn at lists.quickfixn.com
>> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>>
>
>
>
> --
> Grant Birchmeier
> Connamara Systems, LLC
> Made-To-Measure Trading Solutions.
> Exactly what you need. No more. No less.
> http://connamara.com
>
>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>