Lines Matching refs:has
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
45 SSL_shutdown() should not be called if a previous fatal error has occurred on a
46 connection; i.e., if L<SSL_get_error(3)> has returned B<SSL_ERROR_SYSCALL> or
94 prior to initiating the shutdown has been read. An application should handle
111 complete (for example, because a close_notify alert message has not yet been
131 it is called when the application has not read all pending application data
181 application protocol in use enables the peer to ensure that all data has been
199 when all data has been received.
203 which indicates unambiguously when all data has been sent.
283 data written to a stream by an application has been acknowledged by the peer. In
285 application has been sent to the peer, and until the receipt of all such data is
298 condition has occurred and the delivery of data written to streams via
334 know that the connection has terminated until the negotiated idle timeout (if
337 This will generally return 0 on success, indicating that the connection has not
338 yet been fully shut down (unless it has already done so, in which case it will
357 either success or failure depending on whether a shutdown has occurred.
359 If a locally initiated shutdown has already been triggered or the connection has
360 started terminating for another reason, this flag has no effect.
382 The shutdown process is ongoing and has not yet completed.
384 For TLS and DTLS, this means that a close_notify alert has been sent but the
385 peer has not yet replied in turn with its own close_notify.
388 sent but the connection closure process has not yet completed.
402 has completed.
