arturobernalg commented on PR #581: URL: https://github.com/apache/httpcomponents-core/pull/581#issuecomment-3636527889
> @arturobernalg @rschmitt This timeout value / these timeout values must be settable / mutable at runtime exactly the same way as Socket read timeout. Just setting an initial value from a config bean is not good enough. At the client level the request execution pipeline could use that API to apply `RequestConfig#responseTimeout` at the initiation of the message exchange @ok2c Makes sense. I can treat the timeouts in H2Config as defaults and keep the actual per-stream timeout state on H2Stream. I will expose a small control API on H2StreamChannel so the client execution pipeline can set / mutate idle / lifetime timeouts at the start of an exchange and map RequestConfig#responseTimeout to the stream lifetime there. -- 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]
