Lines Matching refs:blocking
83 complete (either blocking, or failing appropriately if nonblocking mode is
173 and L<SSL_write(3)> operated in a blocking fashion was directly correlated with
174 whether the underlying network socket was configured in a blocking fashion. This
176 application-level blocking mode using L<SSL_set_blocking_mode(3)>. See
182 application can still enjoy blocking semantics for calls to application-level
185 in nonblocking mode. For application-level blocking functionality, see
387 desired. Implementing these methods is required if blocking semantics at the SSL
395 in blocking mode or not. Traditionally, an SSL object has automatically operated
396 in blocking or nonblocking mode based on whether the underlying network BIO
397 operates in blocking or nonblocking mode. QUIC requires the use of a
398 nonblocking network BIO, therefore the blocking mode at the application level
400 L<SSL_set_blocking_mode(3)> API. The default mode is blocking. If an application
402 it must add a call to L<SSL_set_blocking_mode(3)> to disable blocking mode.
409 SSL object is used in blocking mode, an ongoing blocking call to an I/O function
456 Whether the application will use blocking or nonblocking I/O at the application
531 Configures whether blocking semantics are used at the application level. This
621 remotely-initiated QUIC stream, blocking until one is available if the
719 to use the SSL APIs in a blocking fashion, but is also designed to facilitate
