Bidirectional control stream
kixelated opened this issue · comments
The current transport API uses unidirectional streams only. The MoQ Transport (#27) adds a bidirectional stream for the SETUP message, but then it uses an unspecified number of unidirectional streams going forward.
We should just use a single bidirectional streams for all control messages (moq-wg/moq-transport#138). It makes the implementation dramatically simpler, avoids handshake race conditions, and is similar to how HTTP/3 works. We should do it despite the draft lagging.