ef85356f45
non-blocking connect is available for writing (i.e. the connection was successful) when the connection has actually failed. This caused synergy to rapidly retry connecting. This change makes synergy check for a connection error whether one was reported or not. Thankfully, OS X does correctly set the socket error state when it bogusly reports a successful connection so we can tell the connection failed. |
||
|---|---|---|
| .. | ||
| arch | ||
| base | ||
| client | ||
| common | ||
| io | ||
| mt | ||
| net | ||
| platform | ||
| server | ||
| synergy | ||
| Makefile.am | ||