[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-dev] Information regarding Jetty HTTP Client properties
|
Hi,
On Wed, Apr 19, 2017 at 7:13 PM, Neha Munjal <neha.munjal3@xxxxxxxxx> wrote:
> Hi,
>
> We are working with Jetty 9.4.3.v20170317 distribution and using the low
> level HttpClient API to create Http2Client objects to be able to do HTTP/2
> communication both synchronously and asynchronously.
Given the properties below, you are using the *high* level HttpClient.
The low level one does not have, for example, the
"addressResolutionTimeout" property.
> Since, we could not find much information for all the properties in the API
> documentation, I would like to clarify the usage of following 2 properties
> that can be set on the client object:
>
> 1. IdleTimeout: How does this property behave? In case a connection becomes
> idle, i.e no data exchange from either side, is this connection just added
> back to the list of idle connection in the underlying connection pool?
No, the connection is closed.
> We have a use case wherein we would just create 1 connection and stream
> requests, so we would like to understand if a connection became idle and
> say, we have a new incoming request to make HTTP communication, would we use
> this connection and activate it so that it could be used for the exchange?
After the idle timeout, if a new request comes in it will trigger the
creation of a new connection.
> Also if this property is not explicitly configured, does it assume some
> default value?
Yes.
> 2. AddressResolutionTimeout: What is the significance to set this timeout
> property? We do set the connection timeout. If addressResolutionTimeout is
> not explicitly set, does this property default to connection timeout?
This is the timeout for DNS resolution, that is to resolve the host
name in string form to an IP address.
Once the host name is resolved, it can be used to open a connection,
where the connectionTimeout applies.
Therefore, the addressResolutionTimeout and the connectTimeout are not
related (much).
--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.
