{"push_id":1383440336,"size":1,"distinct_size":1,"ref":"refs/heads/mono-4.8.0-branch","head":"972c7e89989384b6857e2adfabdc54dfc0f6cb65","before":"a87e8cd4a9dd39562c3679448e69500148468168","commits":[{"sha":"972c7e89989384b6857e2adfabdc54dfc0f6cb65","author":{"name":"Ludovic Henry","email":"5bdd6c0d566ae0e63055ef91e0937e26a16e999f@xamarin.com"},"message":"Remove exception when using SO_REUSEADDR on Linux (#3856) (#3873)\n\nSO_REUSEADDR and SO_REUSEPORT are fundamentally different. This\r\nexception seems to have been put in place to address the lack of\r\nthe latter on older Linux kernels for TCP. However, the change in\r\nfact raises an exception when SO_REUSEADDR is used, which causes\r\nfailures in server applications, which may use SO_REUSEADDR to\r\navoid WAIT state timeouts.\r\n\r\nDescription of SO_REUSEADDR and SO_REUSEPORT differences:\r\n\r\nhttp://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t\r\n\r\nSome problems caused by raising this exception:\r\n\r\nhttps://github.com/zeromq/netmq/issues/623\r\nhttps://github.com/zeromq/netmq/issues/592\r\nhttps://github.com/fsprojects/IfSharp/issues/90","distinct":true,"url":"https://api.github.com/repos/mono/mono/commits/972c7e89989384b6857e2adfabdc54dfc0f6cb65"}]}
{"actor":{"display_login":"ludovic-henry"}}