Lines Matching +full:- +full:single +full:- +full:end
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
22 - After the data is passed via SSL_read() to the application the stored
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 -----------------------------
61 See the [Other considerations](#other-considerations) section below.
64 -----------------------------------------------
66 ### Front End I/O API
93 function above and the [Other considerations](#other-considerations) section
97 ----------------------
105 Each SFRAME_LIST item has range.start and range.end values greater
106 than the range.start and range.end values of the previous item in the list.
108 Any redundant frames are released. Insertion at the end of the list
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
128 in the single-copy scenario.
143 Because in MVP only a single bidirectional stream to receive