hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] Moved: (HTTPASYNC-10) Implement client-side async HTTP connection manager
Date Wed, 07 Feb 2007 17:36:05 GMT

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

Oleg Kalnichevski moved HTTPCORE-25 to HTTPASYNC-10:

    Fix Version/s:     (was: 4.0-alpha4)
      Component/s:     (was: HttpCore NIO)
              Key: HTTPASYNC-10  (was: HTTPCORE-25)
          Project: HttpComponents Async  (was: HttpComponents Core)

> Implement client-side async HTTP connection manager
> ---------------------------------------------------
>                 Key: HTTPASYNC-10
>                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-10
>             Project: HttpComponents Async
>          Issue Type: New Feature
>          Components: HttpAsync
>            Reporter: Oleg Kalnichevski
>             Fix For: 1.0-alpha1
> 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.
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

View raw message