Added by bju over 11 years ago. Updated almost 11 years ago.
0%
Description
If the client command produces very much data, the response stream stops in the middle of the answer.
This can be reproduced using telnet. After pressing Enter the response stream will be continued.
So this was not related with the compression? I have noticed this problem, after I have merged the code from compression branch.
Yes and no. The error was introduced with the compression, but not related to the compression itself. A long answer is written in multiple chunks, but the test for existence of a next chunk was wrong. So the next chunk was not sent immediately after the socket was accepting data again. Sending another command (or a simple Return) has also triggered a flush of the remaining data resulting in sending the next chunk.
@Lado: I've tested this now with the command "cevents" resulting in more than 50000 answer lines and there was no blocking. If this works for you also, I think then the bug can be closed.