- From: Jason Greene <jason.greene@redhat.com>
- Date: Mon, 7 Jul 2014 19:11:14 -0500
- To: Roberto Peon <grmocg@gmail.com>
- Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, Johnny Graettinger <jgraettinger@chromium.org>, Mike Bishop <Michael.Bishop@microsoft.com>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
On Jul 7, 2014, at 5:38 PM, Roberto Peon <grmocg@gmail.com> wrote: > You're conflating things. > Timeouts when receiving metadata/headers is an issue regardless of the use large frames or continuations, as a promise of X bytes (or a complete header) doesn't mean it will actually happen, or that it will happen in a reasonable period of time. > This is an issue with both large frames and continuations. It is not limited solely to continuations. The promise is significantly easier to meet though because its limited, especially by default where the limit is 16K. You can of course still have a total connection stall, but that affects all streams anyway. What the limit does is improve the quality of the multiplexing. -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat
Received on Tuesday, 8 July 2014 00:11:58 UTC