Lines Matching refs:not
17 this does not count retransmissions; thus, if a byte is sent, lost, and sent
26 have not, as the peer may wait indefinitely for us to send more data before
36 important than they first appear, as peers are not allowed to rely on them. (For
37 example, a peer is not allowed to wait until we send `DATA_BLOCKED` to increase
41 However, their implementation is not critical.
43 Note that it follows from the above that the CRYPTO-frame stream is not subject
63 payload, the first time it is sent (retransmissions do not count).
70 peers to transmit not just at the rate that our QUIC implementation can
79 and never decreases. On the RX side, such bytes have not necessarily been
96 SWM, not the old CWM.)
120 the number of bytes of STREAM frame payload which are not retransmissions). This
148 We must not exceed the flow control limits, else the peer may terminate the
188 controllers. Callers do not pass the event themselves. The event is generated by
243 this API can be monotonic and thus easier to use (the caller does not need to
257 but not decreasing it, a simple approach which we adopt here.