Lines Matching refs:SSL_read
55 associated with it. Calls to L<SSL_read(3)> and L<SSL_write(3)> on the QUIC
58 L<SSL_read(3)> or L<SSL_write(3)> is called first.
72 connection SSL object; L<SSL_read(3)> and L<SSL_write(3)> calls to the QUIC
81 mode, if a client application calls L<SSL_read(3)> first before any call to
83 is using a server-initiated stream, and the L<SSL_read(3)> call will not
86 application calls L<SSL_write(3)> before any call to L<SSL_read(3)> on the
109 and attempts to call L<SSL_read(3)> and L<SSL_write(3)> on the QUIC connection
112 receiving application data using L<SSL_read(3)> and L<SSL_write(3)>.
126 Most SSL APIs, such as L<SSL_read(3)> and L<SSL_write(3)>, function as they do
173 Traditionally, whether the application-level I/O APIs (such as L<SSL_read(3)>
184 I/O functions such as L<SSL_read(3)> and L<SSL_write(3)>, but the underlying
415 L<SSL_read(3)> or L<SSL_write(3)>), or the new function L<SSL_handle_events(3)>,
420 Most applications will service the SSL object by calling L<SSL_read(3)> or
511 L<SSL_handle_events(3)> (or another I/O function such as L<SSL_read(3)> or
523 functions on an SSL object, such as L<SSL_read(3)> and L<SSL_write(3)>,
605 determines whether calls to functions such as L<SSL_read(3)> and L<SSL_write(3)>
775 I/O function such as L<SSL_read(3)> or L<SSL_write(3)> is called by the