Lines Matching refs:to
18 timeout events which have become due, or may attempt, to the extent currently
19 possible, to perform network I/O operations on one of the BIOs underlying the
22 The primary use case for SSL_handle_events() is to allow an application which uses
23 OpenSSL in nonblocking mode to give OpenSSL an opportunity to handle timer
24 events, or to respond to the availability of new data to be read from an
25 underlying BIO, or to respond to the opportunity to write pending data to an
35 events to be handled properly. This is equivalent to a call to
41 calls to L<SSL_get_event_timeout(3)>; event handling is not performed
42 automatically by calls to other SSL functions such as L<SSL_read(3)> or
43 L<SSL_write(3)>. Note that this is different to QUIC which also performs event
49 timeout events to be handled properly, as well as incoming network data to be
50 processed, and queued outgoing network data to be written, if the underlying BIO
51 has the capacity to accept it.
54 need to call SSL_handle_events() because OpenSSL performs ticking internally on an
57 periodically to allow timeout events to be handled. An application can find out
58 when it next needs to call SSL_handle_events() for this purpose (if at all) by calling
63 will be made to the object for a substantial period of time. So long as at least
64 one call to the SSL object is blocking, no such call is needed. However,
68 it is unnecessary to call SSL_handle_events() as the assist thread handles the QUIC
