| Commit | Date | |
|---|---|---|
|
[r5512]
by
david_costanzo
Document that NETACCEPTON can accept connections from multiple clients. |
2020-12-11 03:39:25 | Tree |
|
[r5511]
by
david_costanzo
Remove false information from NETCONNECTON/NETACCEPTON. |
2020-12-11 03:12:07 | Tree |
|
[r5510]
by
david_costanzo
Fix a race between NETCONNECTON and NETSHUTDOWN wrt async DNS lookup The fix is to store the handle from WSAAsyncGetHostByName so that it can be cancelled in NETSHUTDOWN if it hasn't yet completed. This fix was probably always needed, but it became more apparent recently as the network tests started to deadlock on a call to NETSHUTDOWN when all tests were run. I expect that this fixes the real root cause of Bug #307. |
2020-12-09 22:14:57 | Tree |
| 2020-12-09 20:59:41 | Tree | |
|
[r5508]
by
david_costanzo
Update call to WSAStartup to follow practices recommended on docs.microsoft.com |
2020-12-09 20:51:41 | Tree |
|
[r5507]
by
david_costanzo
Refactoring: extract CServerNetworkConnection::AcceptNewConnection() |
2020-12-09 20:34:04 | Tree |
|
[r5506]
by
david_costanzo
Refactoring: Stop passing a HWND as parameters in the network API. |
2020-12-09 04:43:57 | Tree |
| 2020-12-09 04:09:23 | Tree | |
|
[r5504]
by
david_costanzo
Minor improvements: |
2020-12-09 04:04:38 | Tree |
|
[r5503]
by
david_costanzo
Fix a problem where if a second connection was created to a NETACCEPTON server while it was already connected, then winsock would not raise any more FD_ACCEPT events and the server wouldn't be able to process any further connections. The fix is to a set flag when NETACCEPTON is too busy to accept a second connection, then to later execute accept() once the first connection is closed. |
2020-12-09 04:00:53 | Tree |