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
In h3, it's possible that the qpack encoder stream could get blocked. When that happens, we will want to send literals rather than block. If we block on the encoder stream, we also have to block the request stream. In order to test this, we need a way to ask the stream how much flow control credit it has.
This should also check the connection-level flow control.
The text was updated successfully, but these errors were encountered:
Gives a way for applications to know at least how much they can send
without hitting flow control. (They may still hit pacing and tx buffer
limits, of course.)
fixesmozilla#31
In h3, it's possible that the qpack encoder stream could get blocked. When that happens, we will want to send literals rather than block. If we block on the encoder stream, we also have to block the request stream. In order to test this, we need a way to ask the stream how much flow control credit it has.
This should also check the connection-level flow control.
The text was updated successfully, but these errors were encountered: