[
https://issues.apache.org/jira/browse/HTTPCLIENT-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Weber resolved HTTPCLIENT-689.
-------------------------------------
Resolution: Fixed
I've slightly revised my plan for the next step. Parameter stack building is
moved to AbstractHttpClient,
but the DefaultClientRequestDirector keeps it's params attribute and
constructor argument. Instead
of the plain client parameters, it is initialized with the params stack created
by the client.
On first glance, it seems to me that the behavior of the director becomes more
predictable this way.
It doesn't switch between using client-only params and the params stack created
for the request.
cheers,
Roland
> stackable parameters
> --------------------
>
> Key: HTTPCLIENT-689
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-689
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Reporter: Roland Weber
> Assignee: Roland Weber
> Priority: Minor
> Fix For: 4.0 Alpha 2
>
>
> Implement "stackable parameters" to allow for a parameter hierarchy without
> linking params instances.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
