hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1656) Client Builder doesn't expose setValidateAfterInactivity(int)
Date Thu, 04 Jun 2015 12:08:38 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572646#comment-14572646

Oleg Kalnichevski commented on HTTPCLIENT-1656:

I assigned the issue to 5.0, did not I? This is all I can do at the moment. If for whatever
reason we decide to release 4.6 before 5.0, I'll re-assign this issue to 4.6.


> Client Builder doesn't expose setValidateAfterInactivity(int)
> -------------------------------------------------------------
>                 Key: HTTPCLIENT-1656
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1656
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpClient
>    Affects Versions: 4.4.1
>            Reporter: yair ogen
>            Priority: Minor
>             Fix For: 5.0
> The API 'setStaleConnectionCheckEnabled' on the RequestConfig Builder is deprecated.
It points to calling 'setValidateAfterInactivity' on the PoolingHttpClientConnectionManager
> However we shouldn't mandate creating our own PoolingHttpClientConnectionManager instance
(instead of reusing the one created automatically by the httpClient builder) just to setValidateAfterInactivity.
> We should expose on the client/request config builder a setValidateAfterInactivity like
we do for 'setMaxConnPerRoute' and 'setMaxConnTotal' (which in the builder are later set on
the internally created PoolingHttpClientConnectionManager ).

This message was sent by Atlassian JIRA

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

View raw message