Where the \r and the \n of the Client::MSG_SEPARATOR string appear in separate packets received from a client's socket, this is not currently handled by the Client::dataRecv() method and instead the server appears then to hang, expecting more data from the client.
This pull request allows this edge case to be handled correctly.
Where the
\r
and the\n
of theClient::MSG_SEPARATOR
string appear in separate packets received from a client's socket, this is not currently handled by theClient::dataRecv()
method and instead the server appears then to hang, expecting more data from the client.This pull request allows this edge case to be handled correctly.