Sorry, forgot to attach the C++ example.
-Aron
On Tue, Apr 21, 2009 at 2:22 PM, Aron Bierbaum wrote:
> I have been able to reproduce the same results with a simple C++
> example. I have been unable to find any specific reason why binding to
> "127.0.0.1" and later callin
ockname())
to
client.connect(('127.0.0.1', server.getsockname()[1]))
On Mon, Apr 20, 2009 at 7:06 PM, Jean-Paul Calderone wrote:
> On Mon, 20 Apr 2009 18:16:39 -0500, Aron Bierbaum
> wrote:
>>
>> I have looked into this a little more and have noticed that if I
>>
his in the next couple of days.
-Aron
On Mon, Mar 9, 2009 at 9:36 AM, Jean-Paul Calderone wrote:
> On Mon, 9 Mar 2009 09:17:14 -0500, Aron Bierbaum
> wrote:
>>
>> I have been unable to reproduce this problem on multiple machines that
>> I have tested on. Also I have
wrote:
> On Thu, 5 Mar 2009 16:49:15 -0600, Aron Bierbaum
> wrote:
>>
>> I have been using a custom Qt4 reactor that derives from
>> PosixReactorBase. As a result it creates a _Win32Waker to allow
>> threads and signals to wake up the IO thread. It seems though that the
I have been using a custom Qt4 reactor that derives from
PosixReactorBase. As a result it creates a _Win32Waker to allow
threads and signals to wake up the IO thread. It seems though that the
current implementation only works about half of the time. The other
half it exists with :
File "...\Lib\
