mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vishant Singh (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MESOS-6127) Implement suppport for HTTP/2
Date Mon, 05 Sep 2016 16:33:20 GMT

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

Vishant Singh edited comment on MESOS-6127 at 9/5/16 4:33 PM:
--------------------------------------------------------------

just curious 
-how multiplexing is new while one can use http persistent connections? kind of re-using the
same tcp connection....
-header compression between master-agent does it have overhead considering the header data
we want to compress?
-compression+TLSencryption b/w master and agent would not add to do agent timeouts/re-registrations/registrations
to master?
(sorry for being bit negative here)


was (Author: vishant.singh@gmail.com):
just curious 
-how multiplexing is new while could use http persistent connections? kind of re-using the
same tcp connection....
-header compression between master-agent does it have overhead considering the header data
we want to compress?
-compression+TLSencryption b/w master and agent would not add to do agent timeouts/re-registrations/registrations
to master?
(sorry for being bit negative here)

> 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