Lines Matching full:blocking

152 .SH "BLOCKING I/O CAPABILITIES"
153 .IX Header "BLOCKING I/O CAPABILITIES"
154 All of the supported concurrency models are capable of supporting blocking I/O
157 serviced. This includes the use of \fBSSL_poll\fR\|(3) in a blocking fashion.
159 Supporting blocking API calls reliably with multi-threaded usage requires the
164 the chosen concurrency model, blocking API calls may not be available and calls
165 to \fBSSL_set_blocking_mode\fR\|(3) attempting to enable blocking mode may fail,
167 .SS "Legacy Blocking Support Compatibility"
168 .IX Subsection "Legacy Blocking Support Compatibility"
169 OpenSSL 3.2 and 3.3 contained a buggy implementation of blocking QUIC I/O calls
176 concurrency model or disable it. This is known as Legacy Blocking Compatibility
188 concurrency model and b) explicitly opt in or out of blocking I/O support
189 (depending on whether the application wishes to make blocking I/O calls),
190 disabling Legacy Blocking Compatibility Mode.
217 Enable reliable support for blocking I/O calls, allocating whatever OS resources
225 Enables legacy blocking compatibility mode. See "Legacy Blocking Support
248 \&\fBSSL_DOMAIN_FLAG_BLOCKING\fR flag. This provides reliable blocking functionality.
271 If full blocking I/O support is selected using \fBSSL_DOMAIN_FLAG_BLOCKING\fR, at
273 allow one thread to wake other threads which may be blocking in calls to OS
293 A QUIC SSL object has blocking mode enabled by default where \fBall\fR of the
302 In all other cases, a QUIC SSL object has blocking mode disabled by default. The
303 blocking mode can be changed explicitly using \fBSSL_set_blocking_mode\fR\|(3).