[
https://issues.apache.org/jira/browse/HTTPCLIENT-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arturo Bernal resolved HTTPCLIENT-2429.
---------------------------------------
Fix Version/s: 5.7-alpha2
Resolution: Fixed
> Improve support for custom transport layers
> -------------------------------------------
>
> Key: HTTPCLIENT-2429
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2429
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Reporter: Arturo Bernal
> Priority: Minor
> Fix For: 5.7-alpha2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> HttpClient currently provides limited extension points for applications that
> need to use custom transport layers.
> The classic client already has DetachedSocketFactory, which has been used by
> applications to implement transports such as Unix domain sockets and named
> pipes. However, using it as a general-purpose transport extension point
> currently requires relying on internal / experimental APIs.
> The async client does not currently provide an equivalent HttpClient-level
> extension point.
> The goal of this issue is to improve and stabilize custom transport support:
> * provide a supported extension point for custom transports in the classic
> client, preferably by stabilizing / generalizing DetachedSocketFactory;
> * provide an equivalent capability for the async client, reusing existing
> HttpCore abstractions such as ConnectionInitiator where appropriate;
> * avoid adding transport-specific special cases to HttpClient;
> * preserve existing TCP, TLS and Unix domain socket behavior and
> compatibility.
> The intention is to allow applications to integrate transports such as named
> pipes or proprietary intra-DC protocols without requiring HttpClient itself to
> implement those transports.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
