- From: <K.Morgan@iaea.org>
- Date: Fri, 11 Jul 2014 20:12:58 +0000
- To: <martin.thomson@gmail.com>
- CC: <gregw@intalio.com>, <jpinner@twitter.com>, <ietf-http-wg@w3.org>
Hi Martin- I think that 5 is a non-starter. Roberto's analysis on this has convinced me that this is an undesirable feature. What does... 5) Allowing interleaving of CONTINUATION frames with other frames. ...have to do with Roberto's analysis? Are you referring to his #1, unfinished header sets? That is solved by removing the reference set. Each HEADERS/PUSH_PROMISE/CONTINUATION frame can be interleaved with other frames from other streams so long as the aforementioned frame types are processed in order. (I don't buy that preventing state-changing hpack opcodes from crossing frame boundaries is so hard. If the *uncompressed* size of the next header is too big to fit in the remaining space, then finish up the current frame and start a new one.) -Keith This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
Received on Friday, 11 July 2014 20:13:56 UTC