diff options
author | Eric Wong <e@80x24.org> | 2016-05-30 04:39:57 +0000 |
---|---|---|
committer | Eric Wong <e@80x24.org> | 2016-05-30 04:46:23 +0000 |
commit | 56692b57c4e6a404fee0ec8eef857f35e09ce767 (patch) | |
tree | ba5a3c77f8995122110fa18780b47cad5618c81b /script | |
parent | 1cf14fe543ad6259003cdd1995a1c83a7a70b535 (diff) | |
download | public-inbox-56692b57c4e6a404fee0ec8eef857f35e09ce767.tar.gz |
http: yield body->getline running time
We cannot let a client monopolize the single-threaded server even if it can drain the socket buffer faster than we can emit data. While we're at it, acknowledge the this behavior (which happens naturally) in httpd/async. The same idea is present in NNTP for the long_response code. This is the HTTP followup to: commit 0d0fde0bff97 ("nntp: introduce long response API for streaming") commit 79d8bfedcdd2 ("nntp: avoid signals for long responses")
Diffstat (limited to 'script')
0 files changed, 0 insertions, 0 deletions