[
https://issues.apache.org/jira/browse/CONNECTORS-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13960020#comment-13960020
]
Karl Wright commented on CONNECTORS-911:
----------------------------------------
Here's the response.
"Neither are wrong. Both ways are largely the same. HttpClientBuilder
creates an instance of PoolingHttpClientConnectionManager internally if
no connection manager has been explicitly set. However if you want to be
able to tweak connection manager settings at runtime the former approach
should be used as you will need a reference to the connection manager to
do so.
If what you want to a single persistent connection have you considered
using BasicHttpClientConnectionManager instead of
PoolingHttpClientConnectionManager?"
It sounds like we should look into how BasicHttpClientConnectionManager
behaves, and maybe substitute that instead of
PoolingHttpClientConnectionManager.
I'd like to come up with a standard way of doing this, and do it the same way
everywhere we need this behavior. How do you think we should do it?
> Work on removing HttpClient 4.3 deprecation warnings
> ----------------------------------------------------
>
> Key: CONNECTORS-911
> URL: https://issues.apache.org/jira/browse/CONNECTORS-911
> Project: ManifoldCF
> Issue Type: Task
> Components: Elastic Search connector, Framework crawler agent, JIRA
> connector, Lucene/SOLR connector, OpenSearchServer connector, RSS connector,
> Web connector, Wiki connector
> Affects Versions: ManifoldCF 1.6
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.6
>
> Attachments: CONNECTORS-911.patch, SolrConnector.patch,
> SolrConnector.patch, SolrConnector.patch
>
>
> HttpClient 4.3 deprecates pretty much the entire way you used to build
> httpclient instances; fixing this requires a lot of work in ManifoldCF.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
