- From: Jason Greene <jason.greene@redhat.com>
- Date: Fri, 21 Nov 2014 11:07:01 -0600
- To: Amos Jeffries <squid3@treenet.co.nz>
- Cc: Andy Green <andy@warmcat.com>, ietf-http-wg@w3.org
> On Nov 21, 2014, at 10:01 AM, Amos Jeffries <squid3@treenet.co.nz> wrote: > > If its a DATA frame then recipients should be handling it as per the > HTTP/2 spec handling regardless of WS knowledge level. The DATA > payload is opaque and may be sliced and diced on any 8-bit boundary > within, so long as the end recipient gets it all in proper order. > (Think DATA approximates TCP DATA packet with HEADERS as the SYN > handshake preceeding it all). I agree. The individual hop has the best understanding of how to optimally format its messages. I could, however, understand a desire to pass a hint as a flag that a particular frame is urgent, and should favor flushing as soon as possible. -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat
Received on Friday, 21 November 2014 17:08:41 UTC