[
https://issues.apache.org/jira/browse/CXF-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502533#comment-14502533
]
Akitoshi Yoshida commented on CXF-6349:
---------------------------------------
I agree with what Sergey says above.
If the netty's http2 option can be integrated into the current netty transport
as an optional feature, that will be an option.
Similarly, if the http2 feature of jetty9 can be integrated into the current
jetty transport, this can also be an option.
If the API differs depending on its version and we need to support those
multiple versions (as we had to do for the jetty-only websocket transport for
jetty8 and jetty9 API), it may get messy at some time.
To get provider/version independency for http2, we can use Atmosphere when it
supports http2. However, this is currently a work in progress.
I think all can coexist and if Leonardo wants to look at the netty variant, he
can start looking into the netty component.
> Introduce HTTP/2 Transport
> ---------------------------
>
> Key: CXF-6349
> URL: https://issues.apache.org/jira/browse/CXF-6349
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Reporter: Sergey Beryozkin
> Fix For: NeedMoreInfo
>
>
> https://http2.github.io/
> Can be complementary to what Aki has done with WebSockets.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
