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

Aaron Wood commented on MESOS-6127:
-----------------------------------

Current design doc is here 
https://docs.google.com/document/d/1vD8x2l5X6LzrHMCIOcWnx8ky_nT_Y2UIrQUXQB7DdLw/edit
I don't have the bandwidth at work to take this on right now but I believe 
[~ipronin] was interested in taking this further.

> 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.
> Some ideas for libs:
> https://nghttp2.org/documentation/package_README.html - Has encoders/decoders 
> supporting HPACK https://nghttp2.org/documentation/tutorial-hpack.html
> https://nghttp2.org/documentation/libnghttp2_asio.html - Currently marked as 
> experimental by the nghttp2 docs



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to