Re: [quicwg/base-drafts] Move stream type into frame type (#1431)

[Mike Bishop <[e-mail]>]

The debugging aspect is mitigated if you stick the type in the top two bits of a 64-bit integer locally.  So you'd see 0x00000002, 0x40000002, 0x80000002, or 0xc0000002.  Or you'd output with a prefix, e.g. CU2, SB2, etc.  But you can't encode that way on the wire, or only one of the types can be less than 4 bytes.

Yeah, I thought about trying to condense it to three types per frame, where one of them means "the only unidirectional stream I could be talking about" and the interpretation varies based on who's sending it.  It's only a step further than the two-type frames that imply directionality based on the sender and only provide bi/uni in a bit.  But I feel like the cost in consistent representation outweighed saving the frame types.  We already have the language that says you need to reject a frame that talks about a stream the sender isn't allowed to talk about, so that's no worse, even if no better.

How does it ruin PRIORITY again?

-- 
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/pull/1431#issuecomment-395780478