Lines Matching refs:SSL_read
23 stream associated with it. Calls to L<SSL_read(3)> and
26 perspective depends on whether L<SSL_read(3)> or L<SSL_write(3)> is called
71 connection SSL object; L<SSL_read(3)> and L<SSL_write(3)> calls to the QUIC
80 mode, if a client application calls L<SSL_read(3)> first before any call to
82 is using a server-initiated stream, and the L<SSL_read(3)> call will not
85 application calls L<SSL_write(3)> before any call to L<SSL_read(3)> on the
108 and attempts to call L<SSL_read(3)> and L<SSL_write(3)> on the QUIC connection
111 receiving application data using L<SSL_read(3)> and L<SSL_write(3)>.
125 Most SSL APIs, such as L<SSL_read(3)> and L<SSL_write(3)>, function as they do
172 Traditionally, whether the application-level I/O APIs (such as L<SSL_read(3)>
183 I/O functions such as L<SSL_read(3)> and L<SSL_write(3)>, but the underlying
407 that it calls an I/O function on the SSL object (for example, L<SSL_read(3)> or
413 Most applications will service the SSL object by calling L<SSL_read(3)> or
504 L<SSL_handle_events(3)> (or another I/O function such as L<SSL_read(3)> or
516 functions on an SSL object, such as L<SSL_read(3)> and L<SSL_write(3)>
532 determines whether calls to functions such as L<SSL_read(3)> and L<SSL_write(3)>
701 I/O function such as L<SSL_read(3)> or L<SSL_write(3)> is called by the
