Lines Matching refs:event
113 ---> event: On TX (numBytes)
114 ---> event: On TX Window Updated (numBytes)
115 <--- event: On TX Blocked
118 The On TX event is passed to the state machine whenever we send a packet.
122 there is no need to pass the event in this case.
124 The On TX Window Updated event is passed to the state machine whenever we have
129 The On TX Window Updated event expresses the CWM (that is, the cumulative
132 Update event is passed to the state machine with a value lower than that passed
133 in any previous such event, it indicates a peer protocol error or a local
138 On TX event and increased by the On TX Window Updated event. In fact, it is
142 The On TX Blocked event is emitted at the time of any edge transition where the
144 non-zero to zero. This always occurs during processing of an On TX event. (This
145 event is intended to assist in deciding when to generate `DATA_BLOCKED`
161 The On TX Window Updated event occurs in response to the `MAX_STREAM_DATA`
166 The On TX Blocked event can be used to decide when to generate
178 ---> event: On RX Controlled Bytes (numBytes) [internal event]
179 ---> event: On Retire Controlled Bytes (numBytes)
180 <--- event: Increase Window (numBytes)
181 <--- event: Flow Control Error
188 controllers. Callers do not pass the event themselves. The event is generated by
190 `numBytes` is the number of controlled bytes we received. (This event is
197 the Flow Control Error event. The connection should be terminated with a
200 The state machine emits the Increase Window event when it thinks that the peer
205 The state machine is passed the On Retire Controlled bytes event when one or
211 Retire Controlled Bytes event should be sent to the state machine when
221 - There is no On RX Controlled Bytes event.
223 - The On Retire Controlled Bytes event may optionally pass the same event
227 - An additional event is added, which replaces the On RX Controlled Bytes event:
229 ---> event: On RX Stream Frame (offsetPlusLength, isFin)
231 This event should be passed to the state machine when a STREAM frame is
236 This event is used to generate the internal On RX Controlled Bytes event to
241 event if a previous such event already had an equal or greater value. The
242 reason this event is used instead of a `On RX (numBytes)` style event is that
