Lines Matching +full:flow +full:- +full:controller

9 ------------------------------------
13 - As packets with stream frames are received in arbitrary frames the
16 - As packets can be received before application calls SSL_read() to read
18 - The application should be able to set the limit on how much data should
19   be stored. The flow controller should be used to limit the peer to not send
20   more data. Without the flow control limit a rogue peer could trigger
21   a DoS via unlimited flow of incoming stream data frames.
22 - After the data is passed via SSL_read() to the application the stored
23   data can be released and flow control limit can be raised.
24 - As the peer can recreate stream data frames when resending them, the
29 -------------------------------------
34 - To support a single copy operation with a future stream read call
41 -----------------------------
47 This function adjusts the current data flow control limit on the `stream`
61 See the [Other considerations](#other-considerations) section below.
64 -----------------------------------------------
82 ### Flow Control
84 The Receive Buffers module provides an appropriate value for the Flow
93 function above and the [Other considerations](#other-considerations) section
97 ----------------------
116 --------------------
119 a single-copy operation a rogue peer could use this to override the stored
121 offset. For example: 1st frame - offset 0 length 1000, 2nd frame -
122 offset 1 length 1000, 3rd frame - offset 2 length 1000, and so on. We
124 effectively raise the stream data flow control limit quadratically.
127 more data than what is allowed by the stream data flow control limit
128 in the single-copy scenario.
130 Although intuitively the MAX_DATA flow control limit might be used to
144 any data will be supported, the MAX_DATA flow control limit should be equal