[
https://issues.apache.org/jira/browse/MESOS-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497621#comment-15497621
]
Aaron Wood edited comment on MESOS-6127 at 9/16/16 10:53 PM:
-------------------------------------------------------------
Also, should these changes go upstream https://github.com/3rdparty/libprocess
and/or directly in Mesos?
[~vinodkone] if you think we should start with HTTP/2 and leave gRPC for later
what are your thoughts on using libnghttp2_asio vs. implementing support
directly into what exists in http.cpp and http.hpp?
was (Author: aaronjwood):
Also, should these changes go upstream https://github.com/3rdparty/libprocess
and/or directly in Mesos?
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
