mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anand Mazumdar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-6127) Implement suppport for HTTP/2
Date Sat, 17 Sep 2016 00:15:20 GMT

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

Anand Mazumdar commented on MESOS-6127:
---------------------------------------

I tried to work on trying to add HTTP2 support partially at this years MesosCon NA hackathon.

You would still need a library that can understand/parse HTTP2 e.g., libnghttp2 etc. as you
had pointed out earlier. The one which we would eventually choose should be ideally be weighted
upon in the design doc. Currently, Mesos uses the [http-parser|https://github.com/nodejs/http-parser]
library which does not understand HTTP2 the last time I had a look at it.

I would be happy to shepherd the work for putting the design document in place for sharing
it with the community.

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

Mime
View raw message