about summary refs log tree commit diff
path: root/src/testsuite/start-server2
diff options
context:
space:
mode:
authorAlexander Barton <alex@barton.de>2020-05-01 22:38:41 +0200
committerAlexander Barton <alex@barton.de>2020-05-04 00:46:56 +0200
commit629a45ee0f4469729f6a9c22a983000fcc39fe61 (patch)
tree36b5c3eeb24dffd24710907aa64fc9e09e2c1f35 /src/testsuite/start-server2
parent8d414b079c1b4b0b8c88c8ab5cf4b27bf0942752 (diff)
downloadngircd-629a45ee0f4469729f6a9c22a983000fcc39fe61.tar.gz
ngircd-629a45ee0f4469729f6a9c22a983000fcc39fe61.zip
Revert "Increase read buffer size for server connections"
This reverts commit c6e3c13f27744971fcb1d2de4e561d3bcdaa5aed.

This sounded like the right approach at first, but I'm not that sure
that it really makes sense to have different sizes of read buffers: the
per-connection read buffer only needs to keep data that is needed to
parse one full command, be it plain text, encrypted and/or compressed.
Then ngIRCd should handle this one command, move leftover data to the
beginning of the buffer and read the next chunk from the network that is
missing to get the next complete command (512 bytes at max).

So I revert this for now and try to fix the logic in Read_Request(),
which is broken nevertheless, as it results in servers becoming
disconnected during "server burst" when "big" lists are transferred.
Diffstat (limited to 'src/testsuite/start-server2')
0 files changed, 0 insertions, 0 deletions