W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: Large Frame Proposal

From: Jason Greene <jason.greene@redhat.com>
Date: Mon, 7 Jul 2014 17:13:54 -0500
Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, Willy Tarreau <w@1wt.eu>, Johnny Graettinger <jgraettinger@chromium.org>, Greg Wilkins <gregw@intalio.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <E63E7C59-A22C-4663-A588-F229CFC91A7D@redhat.com>
To: Roberto Peon <grmocg@gmail.com>

On Jul 7, 2014, at 5:04 PM, Roberto Peon <grmocg@gmail.com> wrote:

> Oy.
> 
> The concept is fairly simple.
> 
> If you need to know the entire size of the headers before one is allowed to send any of it (as would be the case), then one must wait for all of the headers data to arrive (and mutate it) before forwarding.
> Thus, adding at a minimum: header-bytes/bandwidth seconds of latency per gateway (not to mention the additional memory for the buffering).
> I'd expect this to add a 10th of a ms per gateway or so, more on more constrained links.
> 

If itís HTTP/2 you know the length by just quickly reading the inbound header. Or did you mean relaying HTTP/1.1 -> HTTP/2?

--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
Received on Monday, 7 July 2014 22:14:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:09 UTC