Home
last modified time | relevance | path

Searched refs:nonblocking (Results 1 – 25 of 104) sorted by relevance

12345

/third_party/boost/libs/fiber/doc/
Dnonblocking.qbk11 [#nonblocking]
12 [section:nonblocking Integrating Fibers with Nonblocking I/O]
21 In contrast, a nonblocking I/O operation refuses to start at all if it would
29 nonblocking I/O. At the point where the nonblocking I/O is attempted, a return
33 Worse, a nonblocking I/O operation might ['partially] succeed. That means that
/third_party/openssl/doc/man3/
DSSL_do_handshake.pod28 If the underlying BIO is B<nonblocking>, SSL_do_handshake() will also return
34 The action depends on the underlying BIO. When using a nonblocking socket,
61 for nonblocking BIOs. Call SSL_get_error() with the return value B<ret>
DSSL_accept.pod26 If the underlying BIO is B<nonblocking>, SSL_accept() will also return
33 The action depends on the underlying BIO. When using a nonblocking socket,
60 for nonblocking BIOs. Call SSL_get_error() with the return value B<ret>
DSSL_state_string.pod29 When using nonblocking sockets, the function call performing the handshake
33 For both blocking or nonblocking sockets, the details state information
DSSL_set_fd.pod23 inherit the behaviour of B<fd>. If B<fd> is nonblocking, the B<ssl> will
24 also have nonblocking behaviour.
DSSL_connect.pod26 If the underlying BIO is B<nonblocking>, SSL_connect() will also return
33 The action depends on the underlying BIO. When using a nonblocking socket,
75 for nonblocking BIOs. Call SSL_get_error() with the return value B<ret>
DSSL_CTX_set_mode.pod53 avoid the misconception that nonblocking SSL_write() behaves like
54 nonblocking write().
67 In a nonblocking environment applications must be prepared to handle
69 Setting B<SSL_MODE_AUTO_RETRY> for a nonblocking B<BIO> will process
DSSL_set_bio.pod19 nonblocking then the B<ssl> object will also have nonblocking behaviour. This
DSSL_shutdown.pod98 If the underlying BIO is B<nonblocking>, SSL_shutdown() will also return
104 The action depends on the underlying BIO. When using a nonblocking socket,
155 It can occur if an action is needed to continue the operation for nonblocking
DOCSP_sendreq_new.pod46 OCSP_sendreq_nbio() performs nonblocking I/O on the OCSP request context
117 OCSP_sendreq_bio() does not support retries and so cannot handle nonblocking
/third_party/boost/libs/asio/doc/overview/
Dreactor.qbk42 [link boost_asio.examples.cpp03_examples.nonblocking nonblocking example].
/third_party/node/deps/cares/m4/
Dcares-confopts.m457 dnl --enable-nonblocking or --disable-nonblocking, and
64 AC_ARG_ENABLE(nonblocking, optenable
65 AS_HELP_STRING([--enable-nonblocking],[Enable non-blocking communications])
66 AS_HELP_STRING([--disable-nonblocking],[Disable non-blocking communications]),
70 dnl --disable-nonblocking option used
78 dnl --enable-nonblocking option used
/third_party/cares/m4/
Dcares-confopts.m497 dnl --enable-nonblocking or --disable-nonblocking, and
104 AC_ARG_ENABLE(nonblocking, optenable
105 AC_HELP_STRING([--enable-nonblocking],[Enable non-blocking communications])
106 AC_HELP_STRING([--disable-nonblocking],[Disable non-blocking communications]),
110 dnl --disable-nonblocking option used
118 dnl --enable-nonblocking option used
/third_party/curl/lib/vtls/
Dmesalink.c500 int sockindex, bool nonblocking, bool *done) in mesalink_connect_common() argument
554 nonblocking ? 0 : timeout_ms); in mesalink_connect_common()
561 if(nonblocking) { in mesalink_connect_common()
584 (nonblocking && (ssl_connect_2 == connssl->connecting_state || in mesalink_connect_common()
Dgskit.c944 bool nonblocking) in gskit_connect_step2() argument
954 timediff_t timeout_ms = nonblocking? 0: Curl_timeleft(data, NULL, TRUE); in gskit_connect_step2()
964 if(nonblocking) in gskit_connect_step2()
976 if(nonblocking) in gskit_connect_step2()
1082 bool nonblocking, bool *done) in gskit_connect_common() argument
1122 result = gskit_connect_step2(data, conn, sockindex, nonblocking); in gskit_connect_common()
Dwolfssl.c930 bool nonblocking, in wolfssl_connect_common() argument
982 nonblocking?0:timeout_ms); in wolfssl_connect_common()
989 if(nonblocking) { in wolfssl_connect_common()
1010 if(result || (nonblocking && in wolfssl_connect_common()
Dbearssl.c648 bool nonblocking, in bearssl_connect_common() argument
691 nonblocking?0:timeout_ms); in bearssl_connect_common()
698 if(nonblocking) { in bearssl_connect_common()
718 if(ret || (nonblocking && in bearssl_connect_common()
Dmbedtls.c908 bool nonblocking, in mbed_connect_common() argument
960 nonblocking ? 0 : timeout_ms); in mbed_connect_common()
967 if(nonblocking) { in mbed_connect_common()
988 if(retcode || (nonblocking && in mbed_connect_common()
Dgtls.c201 bool nonblocking) in handshake() argument
231 nonblocking?0: in handshake()
239 if(nonblocking) in handshake()
1339 bool nonblocking, in gtls_connect_common() argument
1352 rc = handshake(data, conn, sockindex, TRUE, nonblocking); in gtls_connect_common()
/third_party/libwebsockets/
DREADME.OpenSource9 …mplementing modern network protocols easily with a tiny footprint, using a nonblocking event loop."
/third_party/boost/libs/asio/doc/
DJamfile.v231 cpp03/iostreams cpp03/local cpp03/multicast cpp03/nonblocking cpp03/porthopper
36 cpp11/multicast cpp11/nonblocking cpp11/operations cpp11/socks4 cpp11/ssl
/third_party/libwebsockets/minimal-examples/dbus-client/minimal-dbus-client/
DREADME.md3 This demonstrates nonblocking, asynchronous dbus method calls as the client.
/third_party/boost/libs/mpi/doc/
DJamfile.v227 ../../../boost/mpi/nonblocking.hpp
/third_party/libwebsockets/READMEs/
DREADME.async-dns.md5 Lws now features optional asynchronous, ie, nonblocking recursive DNS
15 lws is nonblocking.
/third_party/boost/libs/fiber/doc/html/
Dfiber_HTML.manifest33 fiber/nonblocking.html

12345