[
https://issues.apache.org/jira/browse/HTTPCLIENT-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCLIENT-2286:
------------------------------------------
Fix Version/s: Stuck
Labels: volunteers-wanted (was: )
Priority: Minor (was: Major)
[~kwin] what we might do instead is provide a classic i/o compatibility layer
on top of the async transport in the future, but presently this is a relatively
low priority objective for me personally as it may involve substantial efforts
with relatively limited benefit.
Oleg
> Support HTTP/2 via Classic APIs
> -------------------------------
>
> Key: HTTPCLIENT-2286
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2286
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient (classic)
> Reporter: Konrad Windszus
> Priority: Minor
> Labels: volunteers-wanted
> Fix For: Stuck
>
>
> Currently HTTP/2 is only support via Async APIs. Classic APIs only leverage
> HTTP/1 or 1.1. Although from a performance perspective only Async APIs
> unleash the power of HTTP/2 for simple use cases there should be support of
> HTTP/2 endpoints even with Classic APIs.
> Compare with the discussion at
> https://lists.apache.org/thread/h6p7rof2vxgt581towc011vqmsortw6h
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
