An Rcon session runs in a dedicated thread and only waits
for data on a blocking socket after the login.
The first login packet must arrive within 1 second since
the creation of the session and it must be a login packet
with the password in it.
If the packet doesn't arrive, its format is wrong or the
password is wrong the session is closed.
Once successfully connected the socket's receive timeout
is set to infinite and the session only waits for remote
commands.
The session never times out and it's only closed when the
remote socket has been closed or a packet with the wrong
format is received.
An Rcon session runs in a dedicated thread and only waits for data on a blocking socket after the login.
The first login packet must arrive within 1 second since the creation of the session and it must be a login packet with the password in it. If the packet doesn't arrive, its format is wrong or the password is wrong the session is closed.
Once successfully connected the socket's receive timeout is set to infinite and the session only waits for remote commands.
The session never times out and it's only closed when the remote socket has been closed or a packet with the wrong format is received.