Lines Matching full:has

99 shutdown process and return 0 to indicate that the shutdown process has not yet
100 completed. Once the shutdown process has completed, subsequent calls to
104 \&\fBSSL_shutdown()\fR should not be called if a previous fatal error has occurred on a
105 connection; i.e., if \fBSSL_get_error\fR\|(3) has returned \fBSSL_ERROR_SYSCALL\fR or
142 prior to initiating the shutdown has been read. An application should handle
158 complete (for example, because a close_notify alert message has not yet been
178 it is called when the application has not read all pending application data
225 application protocol in use enables the peer to ensure that all data has been
242 when all data has been received.
246 which indicates unambiguously when all data has been sent.
317 data written to a stream by an application has been acknowledged by the peer. In
319 application has been sent to the peer, and until the receipt of all such data is
332 condition has occurred and the delivery of data written to streams via
363 know that the connection has terminated until the negotiated idle timeout (if
366 This will generally return 0 on success, indicating that the connection has not
367 yet been fully shut down (unless it has already done so, in which case it will
383 either success or failure depending on whether a shutdown has occurred.
385 If a locally initiated shutdown has already been triggered or the connection has
386 started terminating for another reason, this flag has no effect.
402 The shutdown process is ongoing and has not yet completed.
404 For TLS and DTLS, this means that a close_notify alert has been sent but the
405 peer has not yet replied in turn with its own close_notify.
408 sent but the connection closure process has not yet completed.