Lines Matching +full:3 +full:l

19 it is used in OpenSSL. See L<ossl-guide-quic-introduction(7)> and
20 L<ossl-guide-quic-client-block(7)>.
29 application calling L<SSL_new(3)>.
43 L<SSL_connect(3)> has returned 1), stream B<SSL> objects are created by the
44 application calling L<SSL_new_stream(3)> or L<SSL_accept_stream(3)> (see
45 L</CREATING NEW STREAMS> below).
48 (see L<ossl-guide-libraries-introduction(7)>). In particular most OpenSSL
60 L<SSL_read_ex(3)>, L<SSL_read(3)>, L<SSL_write_ex(3)> or L<SSL_write(3)> and
63 If a client application calls L<SSL_write_ex(3)> or L<SSL_write(3)> first then
65 stream. If a client application calls L<SSL_read_ex(3)> or L<SSL_read(3)>
70 L<SSL_set_default_stream_mode(3)> for further details.
74 stream that is used. This requires calling L<SSL_set_default_stream_mode(3)>
79 An endpoint can create a new stream by calling L<SSL_new_stream(3)>. This
88 L<SSL_get_accept_stream_queue_len(3)> to determine the number of streams that
90 application can call L<SSL_accept_stream(3)> to create a new B<SSL> object for
93 (see L<SSL_set_blocking_mode(3)>).
97 L<SSL_set_incoming_stream_policy(3)> to set the policy to
100 L</THE DEFAULT STREAM> above.
105 calling L<SSL_get_stream_type(3)>. See the man page for further details.
111 using the L<SSL_write_ex(3)>, L<SSL_write(3)>, L<SSL_read_ex(3)> or
112 L<SSL_read(3)> functions. See the man pages for further details.
115 you should call L<SSL_get_error(3)> to find out further details about the error.
128 application calling L<SSL_stream_conclude(3)>. It is an error to attempt to
129 send more data on a stream after L<SSL_stream_conclude(3)> has been called.
132 L<SSL_stream_reset(3)>.
135 L<SSL_free(3)>. An application should not call L<SSL_shutdown(3)> on it since
142 the connection via a call to L<SSL_get0_connection(3)>. Multi-threaded
145 different thread and call L<SSL_get0_connection(3)> from within that thread then
148 object (with the exception of L<SSL_accept_stream(3)> and
149 L<SSL_get_accept_stream_queue_len(3)> which are thread-safe).
154 L<SSL_get_certificate(3)> can be used to obtain a handle on the peer certificate
167 covered on the L<ossl-guide-quic-client-block(7)> page and we assume that you
171 See L<ossl-guide-quic-client-non-block(7)> for more information about writing a
177 L<https://github.com/openssl/openssl/blob/master/demos/guide/quic-multi-stream.c>.
181 As discussed above in L</THE DEFAULT STREAM> we will follow the recommendation
183 the L<SSL_set_default_stream_mode(3)> function and pass in our connection B<SSL>
261 we just repeatedly call L<SSL_read_ex(3)> until that function fails (indicating
284 In a blocking application like this one calls to L<SSL_read_ex(3)> will either
290 L<SSL_read_ex(3)> gave a 0 response code so we call the L<SSL_get_error(3)>
297 The L<SSL_get_stream_read_state(3)> function can be used to distinguish between
346 we requested. To do that we call L<SSL_accept_stream(3)>. Since this is a
374 L<SSL_free(3)>. Optionally we could call L<SSL_stream_conclude(3)> on them if
380 We should not call L<SSL_shutdown(3)> or L<SSL_shutdown_ex(3)> on the stream
389 L<ossl-guide-introduction(7)>, L<ossl-guide-libraries-introduction(7)>,
390 L<ossl-guide-libssl-introduction(7)> L<ossl-guide-quic-introduction(7)>,
391 L<ossl-guide-quic-client-block(7)>
400 L<https://www.openssl.org/source/license.html>.