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/07/20 20:17:06 UTC

[jira] Closed: (HTTPCLIENT-618) Eliminate class HostConfiguration

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roland Weber closed HTTPCLIENT-618.
-----------------------------------

    Resolution: Fixed

HostConfiguration is gone. The biggest problem turned out to be not ThreadSafeClientConnManager, but the parameters with their route/hostconfig-based map of maximum connections allowed. I'll create another issue for revising these parameters.

cheers,
  Roland


> Eliminate class HostConfiguration
> ---------------------------------
>
>                 Key: HTTPCLIENT-618
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-618
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpConn
>            Reporter: Roland Weber
>            Assignee: Roland Weber
>            Priority: Minor
>             Fix For: 4.0 Alpha 2
>
>
> Remove the target host attribute from the HostConfiguration class. This will allow one HostConfiguration object to be used for different targets.
> The problem is that currently MultiThreadedHttpConnectionManager uses HostConfiguration objects as cache keys, which needs to be changed.
> This is a followup to HTTPCLIENT-615.
> 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