Lines Matching full:retry

121 application has to do, it must also be prepared to come back and retry the
125 before), but this does not have to be the case. It can retry at any time.
127 Note that it is important that you retry exactly the same operation that you
131 some other text when you retry the operation.
263 the event of a non-fatal failure, it waits until a retry of the I/O operation
279 In such a case we must retry the same \fBSSL_connect\fR\|(3) call at a later time.
286 \&            continue; /* Retry */
288 \&        goto end; /* Cannot retry: error */
301 we should retry exactly the same \fBSSL_write_ex\fR\|(3) call again. Note that the
304 retry. An optional mode does exist (\fBSSL_MODE_ACCEPT_MOVING_WRITE_BUFFER\fR)
306 one retry to the next. However, in this case, you must still retry exactly the
316 \&            continue; /* Retry */
318 \&        goto end; /* Cannot retry: error */
322 \&            continue; /* Retry */
324 \&        goto end; /* Cannot retry: error */
328 \&            continue; /* Retry */
330 \&        goto end; /* Cannot retry: error */
348 \&                continue; /* Retry */
355 \&                goto end; /* Cannot retry: error */
390 Since we are using a nonblocking socket we might expect to have to retry this
402 \&            continue; /* Retry */
410 \&        goto end; /* Cannot retry: error */