Lines Matching refs:blocking
35 …`SSL_set_blocking_mode`, `SSL_get_blocking_mode`](#-ssl-set-blocking-mode----ssl-get-blocking-mode…
48 - [Notes on Blocking](#notes-on-blocking)
215 **Blocking Considerations:** Blocks until handshake completed if in blocking
225 error occurs if in blocking mode (including the peek functions).
250 (i.e., copied) all data provided, or an error occurs, if in blocking mode. In
374 - If the BIO is non-pollable (see below), application-level blocking mode will
466 Turns blocking mode on or off. This is necessary because up until now libssl has
467 operated in blocking or non-blocking mode automatically as an emergent
468 consequence of whether the underlying network socket is blocking. For QUIC, this
469 is no longer viable, thus blocking semantics at the application level must be
516 non-blocking mode due to a desire to read from or write to the underlying
595 In blocking mode, the function will return once the closure process is
596 complete. In non-blocking mode, `SSL_shutdown_ex` should be called until it
609 In blocking mode, this blocks until at least one `CONNECTION_CLOSE` frame is
610 sent but does not otherwise block. In non-blocking mode, this should be called
615 by initiating a rapid or non-blocking shutdown and continuing to call
620 effect of this flag is to partially disable blocking behaviour in blocking mode,
893 The blocking mode can be configured on each SSL object individually. When a QUIC
894 stream SSL object is created it inherits its blocking state from the currently
895 configured blocking state of the QUIC connection SSL object at the time the
897 connection SSL object can be in blocking mode to allow for blocking
899 non-blocking mode concurrently.
1057 * If the QUIC connection SSL object is configured in blocking mode, this
1434 **Q. Does `ENABLE_PARTIAL_WRITE` interact with blocking mode?**
1436 A. No; this mode is only relevant to non-blocking mode. In blocking mode,
