Re: [Twisted-Python] _Win32Waker

2009-04-21 Thread Aron Bierbaum
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 calling getsockname would result in a different address of "0.0.0.0" I did find one reference [1] that said that using a port number of 0 wil

Re: [Twisted-Python] _Win32Waker

2009-04-21 Thread Aron Bierbaum
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 calling getsockname would resul