Lines Matching full:retry
142 BIO_get_retry_BIO, BIO_get_retry_reason, BIO_set_retry_reason \- BIO retry
171 has insufficient data to return. Check for readability and/or retry the
175 has pending data to write. Check for writability and/or retry the
181 \&\fBBIO_retry_type()\fR returns a mask of the cause of a retry condition
195 \&\fBBIO_set_retry_reason()\fR sets the retry reason for a special condition for a given
212 \&\s-1BIO\s0 types will not request a retry, because the underlying I/O
214 signal a retry then it need not call \fBBIO_should_retry()\fR after a failed
218 retry even if the underlying I/O structure is blocking, if a handshake
219 occurs during a call to \fBBIO_read()\fR. An application can retry the failed
223 While an application may retry a failed non blocking call immediately
231 available and then retry the \s-1BIO\s0 operation. By combining the retry
245 that is they cannot retry after a partial read or write. This is usually
254 \&\fBBIO_retry_type()\fR returns a flag combination presenting the cause of a retry
255 condition or false if there is no retry condition.