Lines Matching full:blocking

126 complete (either blocking, or failing appropriately if nonblocking mode is
198 and \fBSSL_write\fR\|(3) operated in a blocking fashion was directly correlated with
199 whether the underlying network socket was configured in a blocking fashion. This
201 application-level blocking mode using \fBSSL_set_blocking_mode\fR\|(3). See
205 application can still enjoy blocking semantics for calls to application-level
208 in nonblocking mode. For application-level blocking functionality, see
352 desired. Implementing these methods is required if blocking semantics at the SSL
359 in blocking mode or not. Traditionally, an SSL object has automatically operated
360 in blocking or nonblocking mode based on whether the underlying network BIO
361 operates in blocking or nonblocking mode. QUIC requires the use of a
362 nonblocking network BIO, therefore the blocking mode at the application level
364 \&\fBSSL_set_blocking_mode\fR\|(3) API. The default mode is blocking. If an application
366 it must add a call to \fBSSL_set_blocking_mode\fR\|(3) to disable blocking mode.
371 regularly. If the SSL object is used in blocking mode, an ongoing blocking call
407 Whether the application will use blocking or nonblocking I/O at the application
521 Configures whether blocking semantics are used at the application level. This
597 remotely-initiated QUIC stream, blocking until one is available if the
676 to use the SSL APIs in a blocking fashion, but is also designed to facilitate