On Wed 2017-05-03 15:13:43 -0400, Patrick McManus wrote:
> I forgot to mention another potential challenge with the demux approach -
> h2 is not client send first.. typically both sides send SETTINGS
> simultaneously.. and its important to the server not to hold those back
> .5RTT as it can contain a bunch of configuration information (buffer
> sizing, levels of parallelism, extension negotiation, etc..) that it wants
> the client to start honoring asap. (Whether this is actually simultaneous
> boils down to which flavor of tls handshake is done.)
Ah! Thanks for this heads-up. That's definitely an interesting
wrinkle. How does this interact with HTTP/1 clients connecting to the
service? or is it only possible to do this because of the negotiated
ALPN?
If so, perhaps the demuxing needs to be done only when not sending an
alpn of "h2", and the draft can drop the HTTP/2 section. What do you
think?
--dkg
Received on Wednesday, 3 May 2017 23:22:33 UTC