[
https://issues.apache.org/jira/browse/HTTPCORE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464609
]
Oleg Kalnichevski commented on HTTPCORE-25:
-------------------------------------------
Hi Roland
I suspect there will not much common code in blocking and non-blocking versions
of the HTTP connection management components. Let us start hacking in HttpCore
NIO and then see whether HttpConn might be a better home for this code.
Oleg
> Implement client-side async HTTP connection manager
> ---------------------------------------------------
>
> Key: HTTPCORE-25
> URL: https://issues.apache.org/jira/browse/HTTPCORE-25
> Project: HttpComponents Core
> Issue Type: New Feature
> Components: HttpCore NIO
> Reporter: Oleg Kalnichevski
> Fix For: 4.0-alpha4
>
>
> Implement an async (non-blocking) version of the HTTP connection manager
> intended to facilitate the process of creating client connections and to
> enable re-use of persistent connections
> Some API ideas (as discussed on the mailing list)
> (1) the consumer calls the connection manager and registers a request for a
> connection;
> (2) the connection manager checks whether there is an existent connection to
> the requested target host in the pool, and if not, initiates the process of
> creating one;
> (3) at some point of tine the connection manager calls back and returns an
> open connection;
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.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]
