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/09/01 17:35:19 UTC
[jira] Resolved: (HTTPCLIENT-669) introduce HttpRoutePlanner
interface
[ https://issues.apache.org/jira/browse/HTTPCLIENT-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roland Weber resolved HTTPCLIENT-669.
-------------------------------------
Resolution: Fixed
I've moved DefaultHttpRoutePlanner from client to conn, along with the DEFAULT_PROXY parameter.
> introduce HttpRoutePlanner interface
> ------------------------------------
>
> Key: HTTPCLIENT-669
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-669
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient, HttpConn
> Reporter: Roland Weber
> Assignee: Roland Weber
> Fix For: 4.0 Alpha 2
>
> Attachments: firstImpl.patch, secondImpl.patch
>
>
> Define an interface to determine a route for a given target host.
> Create default implementation replacing DefaultHttpClient.determineRoute(...);
> Implementations will need access to params and/or request.
> The interface fits into HttpConn, but DHC.dR(...) uses client parameters.
> Either move parameters to HttpConn, or keep default implementation in HttpClient.
> Alternative implementations could evaluate Java system properties related to proxy settings.
--
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