On Feb 26, 5:54 pm, Joshua J. Kugler [EMAIL PROTECTED] wrote:
Considering that UNIX Network Programming, Vol 1 (by W. Richard Stevens)
recommends _All_ TCP servers should specify [SO_REUSEADDR] to allow the
server to be restarted [if there are clients connected], and that
Greg Copeland wrote:
Is there some history to this of which I'm not aware? Is there a good
reason for it to default to false?
SNIP Greg's very informative reply
Long story short, it is not a bug. It is a feature. The proper
default is that of the OS, which is to ensure SO_REUSEADDR is
On 3/7/07, Joshua J. Kugler [EMAIL PROTECTED] wrote:
Greg Copeland wrote:
Is there some history to this of which I'm not aware? Is there a good
reason for it to default to false?
SNIP Greg's very informative reply
Long story short, it is not a bug. It is a feature. The proper
default
Chris Mellon wrote:
My problem (and the reason I set reuse to True) is this: if I have
connections active when I restart my service, upon restart, the socket
will
fail to bind because there is still a connection in a WAIT state.
This is just the way sockets work on your platform. How
Joshua J. Kugler wrote:
Considering that UNIX Network Programming, Vol 1 (by W. Richard Stevens)
recommends _All_ TCP servers should specify [SO_REUSEADDR] to allow the
server to be restarted [if there are clients connected], and that
self.allow_reuse_address = False makes restarting a server
Considering that UNIX Network Programming, Vol 1 (by W. Richard Stevens)
recommends _All_ TCP servers should specify [SO_REUSEADDR] to allow the
server to be restarted [if there are clients connected], and that
self.allow_reuse_address = False makes restarting a server a pain if there
were
