TCP Server only parsed TCs in case of receive errors
when client closed connection, valid packets remained in ring buffer until next receive error occured
* TCP Server only parsed TCs in case of receive errors
* when client closed connection, valid packets remained in ring buffer until next receive error occured
meierj
added the bug label 2021-10-08 13:56:32 +02:00
muellerr
was assigned by meierj2021-10-08 13:56:32 +02:00
The socket call is made with a non-blocking flag, so TC is also read if the client does not send anything (to be precise, if the recv call would block).
It definitely still makes sense to read the packets when the client closes the connection
The socket call is made with a non-blocking flag, so TC is also read if the client does not send anything (to be precise, if the `recv` call would block).
It definitely still makes sense to read the packets when the client closes the connection
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
muellerr
The socket call is made with a non-blocking flag, so TC is also read if the client does not send anything (to be precise, if the
recvcall would block).It definitely still makes sense to read the packets when the client closes the connection