Lines Matching refs:process
40 shutdown process and return 0 to indicate that the shutdown process has not yet
41 completed. Once the shutdown process has completed, subsequent calls to
52 close_notify alert message. The shutdown process for SSL/TLS and DTLS
68 shutdown process was first initiated by the local application or by the peer.
73 process and causes OpenSSL to try to send a close_notify shutdown alert to the
74 peer. The shutdown process will then be considered completed once the peer
89 If the peer was the first to initiate the shutdown process by sending a
96 turn, completing the shutdown process, though it may choose to write additional
107 peer (returning 1 and completing the shutdown process). Calls to SSL_shutdown()
110 If the underlying BIO is nonblocking and the shutdown process is not yet
114 shutdown process is still ongoing; in this case, a call to L<SSL_get_error(3)>
117 An application can then detect completion of the shutdown process by calling
119 process is complete (with a close_notify alert having both been sent and
145 waiting for the peer's response. This allows for a more rapid shutdown process
151 process, in which both parties send close_notify alerts and SSL_shutdown()
162 this case, the full shutdown process must be performed to ensure
208 reads, OpenSSL may never process new SSL/TLS session tickets sent by the server.
267 QUIC connection SSL object or exits before completing the shutdown process using
284 other words, the shutdown process waits until all data written by the
286 acknowledged by the peer. Only once this process is completed is the shutdown
294 This behaviour of flushing streams during the shutdown process can be skipped by
308 RFC-compliant QUIC connection closure process could take of the order of
320 This is the default behaviour. The shutdown process may take a period of time up
322 closure process to complete much faster in some circumstances but this cannot be
325 In blocking mode, the function will return once the closure process is complete.
327 indicating the closure process is complete and the connection is now fully shut
382 The shutdown process is ongoing and has not yet completed.
388 sent but the connection closure process has not yet completed.
401 For QUIC connection SSL objects, this means that the connection closure process
