You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Roland Weber (JIRA)" <ji...@apache.org> on 2007/08/25 18:09:31 UTC
[jira] Updated: (HTTPCLIENT-673) revise max-per-host configuration
[ https://issues.apache.org/jira/browse/HTTPCLIENT-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roland Weber updated HTTPCLIENT-673:
------------------------------------
Fix Version/s: (was: 4.0 Alpha 2)
4.0 Alpha 3
TSCCM was subject to major refactoring since alpha 1.
Let's give it some time to settle.
> revise max-per-host configuration
> ---------------------------------
>
> Key: HTTPCLIENT-673
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-673
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpConn
> Affects Versions: 4.0 Alpha 1
> Reporter: Roland Weber
> Priority: Minor
> Fix For: 4.0 Alpha 3
>
>
> Max-per-host settings for ThreadSafeClientConnManagers are currently stored in HttpParams, where the parameter value is a map from HttpRoute (formerly HostConfiguration) to Integer. This has several drawbacks:
> 1) maintaining a map as a value in HttpParams doesn't match my understanding of how params should be used
> 2) the maximums based on HttpRoute are really specific to the TSCCM implementation and not a generic parameterization
> some of the options are:
> a) revise to define a more generic parameterization approach
> b) revise into an implementation specific parameterization approach
> c) define an implementation (TSCCM) specific configuration interface and a default implementation keeping the map as run-time data
> cheers,
> Roland
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org