Bug #1325
closedResponse stream is blocked until client sends new data
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.
Updated by herrlado about 11 years ago
So this was not related with the compression? I have noticed this problem, after I have merged the code from compression branch.
Updated by bju about 11 years ago
- Status changed from New to Resolved
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.
Updated by herrlado about 11 years ago
- Status changed from Resolved to Closed
Done and works! Thanks
Updated by herrlado over 10 years ago
- Target version changed from vdr-plugin-vdrmanager-0.10 to vdr-plugin-vdrmanager-0.11