Lines Matching full:streams

72 .SH "QUIC STREAMS"
73 .IX Header "QUIC STREAMS"
81 Separately a connection can have zero or more streams associated with it
82 (although a connection with zero streams is probably not very useful, so
85 object. A stream is logically independent of all the other streams associated
88 streams, e.g. if an application sends data on stream 1 first and then sends some
95 "CREATING NEW STREAMS" below).
125 .SH "CREATING NEW STREAMS"
126 .IX Header "CREATING NEW STREAMS"
135 The peer may also initiate streams. An application can use the function
136 \&\fBSSL_get_accept_stream_queue_len\fR\|(3) to determine the number of streams that
143 When using a default stream OpenSSL will prevent new streams from being
185 .SH "STREAMS AND CONNECTIONS"
186 .IX Header "STREAMS AND CONNECTIONS"
232 \&     * We will use multiple streams so we will disable the default stream mode.
233 \&     * This is not a requirement for using multiple streams but is recommended.
240 .SS "Creating the request streams"
241 .IX Subsection "Creating the request streams"
242 For the purposes of this example we will create two different streams to send
249 \&     * We create two new client initiated streams. The first will be
255 \&        printf("Failed to create streams\en");
259 .SS "Writing data to the streams"
260 .IX Subsection "Writing data to the streams"
261 Once the streams are successfully created we can start writing data to them. In
286 the requests on the two streams. For the sake of simplicity this example does
295 \&    /* Write an HTTP GET request on each of our streams to the peer */
424 .SS "Cleaning up the streams"
425 .IX Subsection "Cleaning up the streams"
426 Once we have finished using our streams we can simply free them by calling
434 objects since those calls should not be used for streams.