Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Non-Blocking TcpSocket doesn't handle partial sends properly #749
When sending a lot of data (or if just unlucky) over a non-blocking TCP connection, calls to
This happens because the for loop that takes care of partial sends in blocking mode terminates prematurely due to -1 being returned with EWOULDBLOCK as is standard with non-blocking sockets.
Since the partial send size is not relayed back to the user, there is no way for them to resume sending where the previous attempt stopped due to not being ready.
This affects sending