<!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 style="">

<p dir="auto">Aha, interesting. I think that's what I mentioned in the mail, when false start is enabled you cannot be sending and receiving at the same time on two threads. That's because the handshake process, may need to send while operation is receive or receive while operation is send. Maybe the patch could be a clarification that false start and early start (applies to tls1.3 servers), cannot be used by concurrent sending and receiving applications without some synchronization.</p>

<p dir="auto">The synchronization could be locking on recv and send operations, until the handshake is complete. The handshake in false start and early start is complete when a recv operation is complete.</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/713#note_144102801">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/8c93d1948ef755246f6d5dea53b16b7f/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/713#note_144102801"}}</script>

</p>

</div>

</body>

</html>