You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 4, 2018. It is now read-only.
SO_EXCLUSIVEADDRUSE and SO_REUSEADDR are a mess on Windows. The only real way to allow a libuv server to behave consistently and robustly (i.e. to ensure that it can actually listen on the port it needs to listen on and can't get clobbered by other programs) is to set SO_EXCLUSIVEADDRUSE. I think libuv should set this for such sockets, probably for both TCP and UDP.
The text was updated successfully, but these errors were encountered:
SO_EXCLUSIVEADDRUSE
andSO_REUSEADDR
are a mess on Windows. The only real way to allow a libuv server to behave consistently and robustly (i.e. to ensure that it can actually listen on the port it needs to listen on and can't get clobbered by other programs) is to setSO_EXCLUSIVEADDRUSE
. I think libuv should set this for such sockets, probably for both TCP and UDP.The text was updated successfully, but these errors were encountered: