mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cody Maloney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-6127) Implement suppport for HTTP/2
Date Mon, 05 Sep 2016 19:13:21 GMT

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

Cody Maloney commented on MESOS-6127:
-------------------------------------

As long as it's a protocol change, why not go to gRPC which is going to have a lot more maintainers
developing / maintaining and committed to it than a HTTP2 + Protobuf thing that Mesos internally
builds.

> 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)

Mime
View raw message