02-06-2012, 09:48 PM
I'd like to question the wisdom of setting the address reuse option for the server (cServer.cpp, line 186 as of rev 234).
The purpose of this API is to allow multiple sockets listen on the same port, for the case when the program originally listening on that port crashes, then a new instance can listen on the same port again while the old tcp endpoint still is in the TIME_WAIT state. However, at least on Windows, this also allows multiple programs to actively listen on the same port at the very same time.
I strongly believe that MCServer should be the only application using the port, and it should end with an error message if that port is already used. Therefore I'd like to remove the Reuse option, at least from windows builds of MCS.
What do you say?
References:
SO_REUSEADDR on unix: http://www.unixguide.net/network/socketfaq/4.5.shtml
SO_REUSEADDR on Win: http://msdn.microsoft.com/en-us/library/...s.85).aspx
The purpose of this API is to allow multiple sockets listen on the same port, for the case when the program originally listening on that port crashes, then a new instance can listen on the same port again while the old tcp endpoint still is in the TIME_WAIT state. However, at least on Windows, this also allows multiple programs to actively listen on the same port at the very same time.
I strongly believe that MCServer should be the only application using the port, and it should end with an error message if that port is already used. Therefore I'd like to remove the Reuse option, at least from windows builds of MCS.
What do you say?
References:
SO_REUSEADDR on unix: http://www.unixguide.net/network/socketfaq/4.5.shtml
SO_REUSEADDR on Win: http://msdn.microsoft.com/en-us/library/...s.85).aspx