[
https://issues.apache.org/jira/browse/MESOS-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497438#comment-15497438
]
Vinod Kone commented on MESOS-6127:
-----------------------------------
It is not trivial to update libprocess (the internal communication library that
mesos uses) to speak gRPC. It might be relatively easier to add support for
HTTP/2 into libprocess. Note that libprocess already supports SSL/TLS when used
in conjunction with libevent. Either way, this needs an extensive design doc.
[~aaronjwood] Is this something you are interested in working on?
> 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)
