You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Arturo Bernal (Jira)" <ji...@apache.org> on 2026/07/23 13:41:00 UTC
[jira] [Assigned] (HTTPCLIENT-2428) Improve capacity management by inflating AsyncDataConsumers
[ https://issues.apache.org/jira/browse/HTTPCLIENT-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arturo Bernal reassigned HTTPCLIENT-2428:
-----------------------------------------
Assignee: Arturo Bernal
> Improve capacity management by inflating AsyncDataConsumers
> -----------------------------------------------------------
>
> Key: HTTPCLIENT-2428
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2428
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient (async)
> Affects Versions: 5.6.2
> Reporter: Oleg Kalnichevski
> Assignee: Arturo Bernal
> Priority: Major
>
> Presently inflating AsyncDataConsumers propagate capacity information of the downstream consumer to the i/o reactor without any adjustment. However, the downstream consumer requesting n bytes of data can easily end up with n * c bytes due to data decompression.
> inflating AsyncDataConsumers should intercept `CapacityChannel` methods and apply an adjustment to the requested data increment to make it more predictable to the downstream consumer. It can be a simple division by c or something more clever.
> More over, InflatingBrotliDataConsumer at present overrides the capacity increment transmitted by the downstream consumer, which looks wrong. This needs to be looked into.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org