[gnutls-devel] GnuTLS | guile: Writes to record ports handle EAGAIN/EINTR transparently. (!1417)

[Read-only notification of GnuTLS library development activities]

civodul commented:


@dueno Good question.  I followed the same strategy as in a229bb36c9592b151f6feb277238c41ab39f40a9.

It's clear that we'd like to loop (or try again later) in the case of `GNUTLS_E_AGAIN` and `GNUTLS_E_INTERRUPTED`.  But are there other non-fatal "errors" that ought to be hidden from the application?

Shouldn't the application have a chance to handle those errors?

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/1417#note_559880529
You're receiving this email because of your account on gitlab.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20210425/80bd5aab/attachment.html>