<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en">
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<title>
GitLab
</title>


<style>img {
max-width: 100%; height: auto;
}
</style>
</head>
<body>
<div class="content">
<div>
<p dir="auto">I don't think that is a problem as long as you update the docs to say that <code>gnutls_record_recv</code> <em>might</em> also send data if needed.</p>
<p dir="auto">Since this will not be default behavior (will only happen when certain flags are provided) it won't break existing code, and those who use these flags know what they're up to.</p>
<p dir="auto">For instance, if I'm working with non-blocking sockets and calling <code>gnutls_record_recv</code> I know I need to check the socket's ready for both reading & writing. If my application is compiled against an older version of GnuTLS that doesn't support this, the code would still work.</p>
</div>


</div>
<div class="footer" style="margin-top: 10px;">
<p style="font-size: small; color: #777777;">

<br>
Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/issues/571#note_106440627">view it on GitLab</a>.
<br>
You're receiving this email because of your account on gitlab.com.
If you'd like to receive fewer emails, you can
<a href="https://gitlab.com/sent_notifications/3294840a9329108c78f0786b80e756bb/unsubscribe">unsubscribe</a>
from this thread or
adjust your notification settings.
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Issue","url":"https://gitlab.com/gnutls/gnutls/issues/571#note_106440627"}}</script>
</p>
</div>
</body>
</html>