[infinispan-issues] [JBoss JIRA] (ISPN-6676) Use HTTP2/Upgrade in HotRod server

[Sebastian Łaskawiec (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-6676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279682#comment-13279682 ] 

Sebastian Łaskawiec commented on ISPN-6676:
-------------------------------------------

Thoughts on design for this feature:

* HTTP/2 [does not support upgrading to another protocol|https://http2.github.io/http2-spec/#rfc.section.8.1.2.2]. [TLS ALPN|https://http2.github.io/http2-spec/#rfc.section.3.1] should be used to ensure this type functionality. 
* HTTP/1.1 Upgrade header is supported to ensure backwards compatibility. In other words we should consider using [HTTP/1.1 Upgrade|https://http2.github.io/http2-spec/#rfc.section.3.2] or [ALPN|https://tools.ietf.org/html/rfc7301] to support this kind of functionality.
* [HTTP/2 client with TLS support must use ALPN|https://http2.github.io/http2-spec/#rfc.section.3.4]
* [HTTP/2 supports extensions, which can use new type of Frames, Settings and Error Codes|https://http2.github.io/http2-spec/#rfc.section.5.5].
* HTTP/2 supports [PING|https://http2.github.io/http2-spec/#rfc.section.6.7] and [CLOSE|https://http2.github.io/http2-spec/#rfc.section.6.8] operations out of the box.
* [ALPN is considered as a protection for cross-protocol attacks|https://http2.github.io/http2-spec/#rfc.section.10.2] for HTTP/2

> Use HTTP2/Upgrade in HotRod server
> ----------------------------------
>
>                 Key: ISPN-6676
>                 URL: https://issues.jboss.org/browse/ISPN-6676
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Cloud Integrations
>            Reporter: Sebastian Łaskawiec
>            Assignee: Sebastian Łaskawiec
>              Labels: hackathon
>
> With HTTP2 it is possible to reuse the same TCP connection and switch into custom binary protocol. This would be a perfect way to cooperate with many load balancers including those deployed in the Cloud.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)