Lines Matching full:blocking

125 =head1 BLOCKING I/O CAPABILITIES
127 All of the supported concurrency models are capable of supporting blocking I/O
130 serviced. This includes the use of L<SSL_poll(3)> in a blocking fashion.
132 Supporting blocking API calls reliably with multi-threaded usage requires the
137 the chosen concurrency model, blocking API calls may not be available and calls
138 to L<SSL_set_blocking_mode(3)> attempting to enable blocking mode may fail,
141 =head2 Legacy Blocking Support Compatibility
143 OpenSSL 3.2 and 3.3 contained a buggy implementation of blocking QUIC I/O calls
150 concurrency model or disable it. This is known as Legacy Blocking Compatibility
169 concurrency model and b) explicitly opt in or out of blocking I/O support
170 (depending on whether the application wishes to make blocking I/O calls),
171 disabling Legacy Blocking Compatibility Mode.
209 Enable reliable support for blocking I/O calls, allocating whatever OS resources
218 Enables legacy blocking compatibility mode. See L</Legacy Blocking Support
248 B<SSL_DOMAIN_FLAG_BLOCKING> flag. This provides reliable blocking functionality.
281 If full blocking I/O support is selected using B<SSL_DOMAIN_FLAG_BLOCKING>, at
283 allow one thread to wake other threads which may be blocking in calls to OS
304 A QUIC SSL object has blocking mode enabled by default where B<all> of the
321 In all other cases, a QUIC SSL object has blocking mode disabled by default. The
322 blocking mode can be changed explicitly using L<SSL_set_blocking_mode(3)>.