Re: [quicwg/base-drafts] qpack: "all" header blocks the decoder started reading (#1409)

[Dmitri Tikhonov <[e-mail]>]

I see.  The draft suggests, however, that the blocked header data remain in its stream's flow control window:

```
                                        While blocked, header field data
   should remain in the blocked stream's flow control window.
```

While it does not say so explicitly, in practice this recommendation means that the header block won't be read (I _think_ -- depends on how it's framed in HQ?), effectively making the stream blocked on a single header block.  (By the way, why is the above `should` and not `SHOULD`?)

Nevertheless, I agree that, technically, there is no restriction not to read in as many header blocks as one desires and have them all block the stream.  I wonder whether the two sentences quoted in the original report could be phrased better.  Feel free to close if you think the current verbiage is OK.  It confused me, though.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1409#issuecomment-394035935