Re: [quicwg/base-drafts] Stream creation order (#634)

[Mike Bishop <[e-mail]>]

I think I can partially explain it.  Each stream for which you're tracking state consumes some memory.  You can elide out large contiguous chunks by saying that:

- Lowest idle stream ID is X
- Of streams < X, any stream not in my state table is closed
- Table contains any idle or open streams < X

If an implementation is implementing tracking in this way, the arrival of stream 200 when X=100 means inserting 100,102,...,198 into the table as idle, then 200 as open.  By mandating that they be used in order, even if reordering occurs, you are less likely to do large chunks of this work at a time (you might get 108 when X=100, but not 200) and if you *do* have to do a large chunk of work the work is still timely because you know all those streams have data in-flight so you would have been doing the work in a few packets anyway.

-- 
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/634#issuecomment-332675911