Agree that #readTimeout would be a clearer name, as #responseTimeout hints at "time to first byte" semantics.

Can you clarify what you mean with readTimeout?
The response timeout setting is applied once the request is sent and removed once the response is received. It doesn't apply to the whole request/response.
The setting doesn't stay in place when the connection is returned to the pool.

If you need idle timeout you need to consider connection pool's maxIdleTime.

https://projectreactor.io/docs/netty/release/reference/index.html#_timeout_configuration

Also, does it make sense to introduce #readTimeout and deprecate these methods as their name is misleading?

^ Similar to this question, after these changes, does it make sense to deprecate the responseTimeout method and introduce maxReadOperationInterval instead (at some point)? :)

Also, does it make sense to introduce #readTimeout and deprecate these methods as their name is misleading?

^ Similar to this question, after these changes, does it make sense to deprecate the responseTimeout method and introduce maxReadOperationInterval instead (at some point)? :)

Please open a new PR and let's discuss it there.

Also, does it make sense to introduce #readTimeout and deprecate these methods as their name is misleading?

^ Similar to this question, after these changes, does it make sense to deprecate the responseTimeout method and introduce maxReadOperationInterval instead (at some point)? :)

Please open a new PR and let's discuss it there.

Sure. Then, I take this as yes to my question. :)

@reactor/netty-team PTAL

@hisener @Stephan202 Thanks for the discussion and the PR!

@simonbasle Thanks for the review