[
https://issues.apache.org/jira/browse/HTTPCORE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCORE-304.
----------------------------------------
Resolution: Fixed
Fix Version/s: 4.2.2
Hi Daniel
I/O reactors used to be configured using HttpParams. Deprecated constructors
are still there. However, I would like to keep low level networking components
decoupled from the HTTP layer as much as possible just to have an option of
releasing them as a separate artifact.
I updated examples in SVN trunk and 4.2.x branch.
Oleg
> NHttpClient example improperly configures connection properties
> ---------------------------------------------------------------
>
> Key: HTTPCORE-304
> URL: https://issues.apache.org/jira/browse/HTTPCORE-304
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: Examples
> Reporter: Daniel Kulp
> Fix For: 4.2.2
>
>
> The NHttpClient.java example referenced from:
> http://hc.apache.org/httpcomponents-core-ga/examples.html
> uses an HttpParam object to set things like the TCP_NODELAY and other
> settings. However, with the NIO based core, those settings are not
> referenced. Those setting have to be set directly on the
> ConnectingIOReactor. (this COULD also be considered a bug in the
> ConnectingIOReactor, maybe it should accept an HttpParam object?)
> In anycase, the example should be updated to reflect configuration that will
> actually work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
