You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Stéphane Cottin (JIRA)" <ji...@apache.org> on 2016/09/05 16:09:20 UTC

[jira] [Commented] (MESOS-6127) Implement suppport for HTTP/2

    [ https://issues.apache.org/jira/browse/MESOS-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15465312#comment-15465312 ] 

Stéphane Cottin commented on MESOS-6127:
----------------------------------------

We're in post-snowden era, TLS is no longer optional for most use cases.

We may also consider supporting the proxy protocol for complex architectures.
http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt 


> Implement suppport for HTTP/2
> -----------------------------
>
>                 Key: MESOS-6127
>                 URL: https://issues.apache.org/jira/browse/MESOS-6127
>             Project: Mesos
>          Issue Type: Epic
>          Components: HTTP API, libprocess
>            Reporter: Aaron Wood
>              Labels: performance
>
> HTTP/2 will allow us to take advantage of connection multiplexing, header compression, streams, server push, etc. Add support for communication over HTTP/2 between masters and agents, framework endpoints, etc.
> Should we support HTTP/2 without TLS? The spec allows for this but most major browser vendors, libraries, and implementations aren't supporting it unless TLS is used. If we do require TLS, what can be done to reduce the performance hit of the TLS handshake? Might need to change more code to make sure that we are taking advantage of connection sharing so that we can (ideally) only ever have a one-time TLS handshake per shared connection.
> Potential library that could be helpful: https://nghttp2.org/documentation/libnghttp2_asio.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)