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

[Dmitri Tikhonov <[e-mail]>]

>  The strict ordering restriction ensures that you can cheaply and reliably determine whether a stream is idle, open, or closed.

I do not see how that is possible.  Here is an example: server receives a request that opens stream 11, yet the largest peer-initiated stream it knows about is 7.  Does it mean that a) client skipped stream 9  -- and thus is in violation of protocol -- or b) previous packet got lost?

> Also, the only reason that you might want to open out of order is if you attached some sort of semantic to the stream ID.

Not necessarily.  One can imagine a scenario in which a multi-threaded program keeps a pool of stream IDs that could be opened and distributes these IDs among threads.  The threads perform some preliminary work -- streams are opened in the same order that these threads complete.

There are probably other reasons why an implementation may want to be able to control the order in which streams are created.

-- 
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-332177520