[ http://issues.apache.org/jira/browse/HTTPASYNC-7?page=all ]
Roland Weber updated HTTPASYNC-7:
---------------------------------
Fix Version/s: 1.1-alpha1
(was: 1.0-alpha1)
> implement connection management for dispatchers
> -----------------------------------------------
>
> Key: HTTPASYNC-7
> URL: http://issues.apache.org/jira/browse/HTTPASYNC-7
> Project: HttpComponents Async
> Issue Type: New Feature
> Components: HttpAsync
> Reporter: Roland Weber
> Assigned To: Roland Weber
> Fix For: 1.1-alpha1
>
>
> Define and implement a connection management interface suitable for
> dispatchers, and dispatchers to use it.
> Connection management for dispatchers is different from that of synchronous
> HttpClient. There, a connection
> is requested for a specific target host and the thread can be blocked until
> one is available. With dispatchers,
> there can be a queue of requests to different hosts. A connection is
> allocated without a specific target, and
> a request/target can be selected by the dispatcher based on the
> connections-to-host limit. If none of the
> requests can be sent without violating these limits the connection should be
> released, but a notification from
> the connection manager is needed to indicate changes that require a new check
> for suitable requests.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://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]
