enowars/enochecker

Timeout should have useful impact

domenukk opened this issue · 1 comments

Right now, the timeout passt to the checker from the Gameserver gets passed to the sockets as-is.
This means, if the checker has 30 seconds to run, takes a second to reach any socket, the socket timeout (still 30 seconds) will never trigger. Instead, the checker is killed.
Instead, we might want to keep track of the remaining time or subtract a bit for each new socket or http connection.

This has been fixed with commit 68ba6c5