You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Split WT_INITIAL_MAX_STREAM_DATA_BIDI into LOCAL/REMOTE
Summary:
The h2 WebTransport draft defines three per-stream data limits (UNI, BIDI_LOCAL
and BIDI_REMOTE) but we only have one BIDI setting at `0x2b63`, which is really
BIDI_LOCAL under an older name. With a single value a bidi stream gets whichever
limit happens to be stored, regardless of which endpoint opened it. Rename
`0x2b63` to `WT_INITIAL_MAX_STREAM_DATA_BIDI_LOCAL`, add `_BIDI_REMOTE` at
`0x2b66`, and split the `WtConfig` fields so `initStreamRecvFc` and
`initStreamSendFc` can pick based on the initiator. As a side effect
`QmuxConnector::makeWtConfig` becomes a straight mapping of the QUIC transport
params it was already reading, instead of discarding two of them.
Reviewed By: hanidamlaj
Differential Revision: D115270998
fbshipit-source-id: 0da72aa6eb1c184bf06f0f59b0c764fd2aa94e93
0 commit comments