arturobernalg commented on PR #663: URL: https://github.com/apache/httpcomponents-core/pull/663#issuecomment-4273954701
> @ok2c The point of the option is independent control of connection-level inbound flow. MAX remains a sensible throughput-oriented default. Smaller values are for applications that want stricter aggregate backpressure across all active streams on a multiplexed connection. > > A concrete use case is an H2 client in a gateway, proxy, or sidecar multiplexing many large upstream responses over a single connection. Such clients may still want a reasonably large per-stream window, while limiting aggregate inbound data in flight at the connection level. To my mind, the main use case is a gateway, proxy, sidecar, API aggregator, or backend-to-backend H2 client multiplexing many concurrent large upstream responses over a single connection. Such clients may want to keep the per-stream window reasonably large, while limiting aggregate inbound data in flight at the connection level for tighter backpressure and more predictable resource usage. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
