[Python-Dev] 2.4 asyncore headache (original) (raw)
Tim Peters tim.peters at gmail.com
Fri Aug 13 22:25:07 CEST 2004
- Previous message: [Python-Dev] 2.4 asyncore headache
- Next message: [Python-Dev] 2.4 asyncore headache
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Tim]
Now somebody, for some reason, added this to 2.4's asyncore.py: if sys.platform == 'win32': reuseconstant = socket.SOEXCLUSIVEADDRUSE
[Andrew]
I'll back out this change.
But only if that's the right thing to do <0.9 wink>. I gave up reading the Windows SO_EXCLUSIVEADDRUSE docs after it got to the "This situation can be quite complicated; even though the socket has been closed, the underlying transport may not terminate its connection ..." part. But by that point, it sure didn't seem like SO_EXCLUSIVEADDRUSE was a plausible Windowsy way to spell the Unixy SO_REUSEADDR ...
- Previous message: [Python-Dev] 2.4 asyncore headache
- Next message: [Python-Dev] 2.4 asyncore headache
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]