Lines Matching refs:SSL_write
24 L<SSL_write(3)> on the QUIC connection SSL object read and write from that
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
81 L<SSL_write(3)> on the connection, it is assumed that the application protocol
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)>.
121 such as L<SSL_write(3)> or L<SSL_get_stream_id(3)> will fail.
125 Most SSL APIs, such as L<SSL_read(3)> and L<SSL_write(3)>, function as they do
173 and L<SSL_write(3)> operated in a blocking fashion was directly correlated with
183 I/O functions such as L<SSL_read(3)> and L<SSL_write(3)>, but the underlying
408 L<SSL_write(3)>), or the new function L<SSL_handle_events(3)>, regularly. If the
414 L<SSL_write(3)> regularly. If an application does not do this, it should ensure
505 L<SSL_write(3)>), if ever.
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
