Fair enough, this mainly sounds like a matter of documentation. I
still think there's some connectTimeout/socketTimeout confusion in the
synchronous client, which I'm working on fixing.

On Fri, Nov 16, 2018 at 2:50 AM Oleg Kalnichevski <ol...@apache.org> wrote:
> I personally do not see a problem here. Connect timeout is not much
> different than socket timeout. It is not an absolute value that defines
> a deadline for the operation. Like the socket timeout, which represents
> the maximum period of time between receipt of two consecutive IP
> packets, the connect timeout represents a maximum period of inactivity
> between two consecutive operations. For instance HttpClient will
> attempt to connect to all available DNS addresses for multi-home DNS
> entries which effectively makes the deadline for the connect operation
> equal n * connectTimeout (where n is the number of IP addresses for the
> DNS entry).
>
> Oleg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to