[
https://issues.apache.org/jira/browse/HTTPCORE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500916#comment-15500916
]
Oleg Kalnichevski commented on HTTPCORE-432:
--------------------------------------------
I just committed the initial implementation of a HTTP/2 stream multiplexer [1]
This is the most essential and complex component feature of HTTP/2 protocol.
Supported features:
* HPACK header compression
* stream multiplexing (client and server)
* flow control
* response push (client and server)
What is likely will not be supported in 5.0-alpha2
* message trailers
* expect-continue handshake
* connection validation (ping)
* automatic re-execution of requests
What is presently not supported and likely will not be supported in 5.0-alpha2
* TLS features
* application-layer protocol negotiation (ALPN)
* Padding in outgoing frames
* Stream priority (may be out of scope for 5.0)
* Plain HTTP/1.1 upgrade (may be out of scope for 5.0)
* CONNECT method (may be out of scope for 5.0)
Oleg
[1]
https://github.com/apache/httpcore/commit/5d3d59f24848383af4778027a868d1433b28c06e
> HttpClient to support HTTP 2.0
> ------------------------------
>
> Key: HTTPCORE-432
> URL: https://issues.apache.org/jira/browse/HTTPCORE-432
> Project: HttpComponents HttpCore
> Issue Type: New Feature
> Components: HttpCore, HttpCore NIO
> Reporter: yair ogen
> Assignee: Oleg Kalnichevski
> Fix For: 5.0-alpha2
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
