You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alexander Rukletsov (JIRA)" <ji...@apache.org> on 2018/01/03 15:32:00 UTC

[jira] [Updated] (MESOS-6127) Implement support for HTTP/2.

     [ https://issues.apache.org/jira/browse/MESOS-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Rukletsov updated MESOS-6127:
---------------------------------------
    Summary: Implement support for HTTP/2.  (was: Implement suppport for HTTP/2)

> Implement support 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
>            Assignee: Ilya Pronin
>              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.
> Some ideas for libs:
> https://nghttp2.org/documentation/package_README.html - Has encoders/decoders supporting HPACK https://nghttp2.org/documentation/tutorial-hpack.html
> https://nghttp2.org/documentation/libnghttp2_asio.html - Currently marked as experimental by the nghttp2 docs



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)