2014/07/09 7:52 "Jeff Pinner" <jpinner@twitter.com>: > > > .... Being required to split the > > HPACK encoding at JUST the right point to fit in a 64k frame is a much > > uglier change than asking "I've generated more than 16k of headers. Does my > > peer support a frame size that this fits in?" > > This isn't really an accurate description. Without the reference set, > HPACK is now streaming so the decision becomes: > > 1) Encode this header into x bytes. > 2) Is x > 64k? This will never work any more, ABORT! > 3) Do x more bytes fit into this frame? > 4a) If yes, add x bytes and increase frame length. > 4b) If no, flush this frame and start a new one. > How does this interact with flow control? If we want to 64K header and peer advertised smaller winfow size we just stuck. Generally I don't think flow control does work well with headers. Best regards, Tatsuhiro Tsujikawa
Received on Wednesday, 9 July 2014 01:13:46 UTC