[
https://issues.apache.org/jira/browse/HTTPCLIENT-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Weber closed HTTPCLIENT-627.
-----------------------------------
Resolution: Fixed
The API in org.apache.http.conn is ready for review. The connection manager
implementations in o.a.h.impl.conn are stuck in transition and need more work.
I'll clean up smaller things while writing test cases and leave the big one
(HTTPCLIENT-636) until we've got test coverage.
In org.apache.http[.impl].client are skeletons for HttpClient and
HttpRequestDirector. They are good enough to make use of the connection
managers and to communicate directly or via tunnelled TLS/SSL through a proxy
as long as no authentication is required.
cheers,
Roland
> overhaul connection manager and associated connection interface
> ---------------------------------------------------------------
>
> Key: HTTPCLIENT-627
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-627
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpConn
> Reporter: Roland Weber
> Assigned To: Roland Weber
> Priority: Critical
> Fix For: 4.0 Alpha 1
>
>
> MultiThreadedHttpConnectionManager/HttpHostConnection needs to be overhauled
> to provide a layer on top of OperatedClientConnection.
> Preliminary working names: ThreadSafeClientConnManager/ManagedClientConnection
> This implies some work on former HttpMethodDirector and HttpClient to verify
> completeness of the new connection management API.
--
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]
