Github user ok2c commented on the issue:
https://github.com/apache/httpcomponents-core/pull/91
> A buffering layer will be mandatory ..., but data only has to be buffered
if the downstream consumer is not ready to process it;
@rschmitt Any notion of content buffering in the session layer makes me
very, very uneasy. Once a chunk of message gets read from the socket channel,
as far as the I/O selector is concerned the data has been fully consumed. It
will no longer have any means of tracking that data. If the application layer
stops reading data and clears interest in input events, the I/O selector will
not be able to trigger read events on the associated channel, if the remaining
message content has been buffered by the session. This problem has caused a lot
of grief in HttpCore 4.x and its resolution involved a fair deal of ugly code.
I was hoping to avoid having to do the same in HttpCore 5.x.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
