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

<blockquote dir="auto">

<p>But in case you have 2 threads sending/receiving during <code>RECV_STATE_FALSE_START_HANDLING</code> or <code>RECV_STATE_EARLY_START_HANDLING</code>, don't you need to block the 2nd thread until the handling is completed? It feels to me like if you don't, you might have 2 threads trying to process the handshake during recv/send</p>

</blockquote>

<p dir="auto">Sending is ok in the <code>RECV_STATE_FALSE_START_HANDLING</code> or the early variant. The only need that sending needs to know is the actual state of the handshake, and if the state is incomplete, to check whether we are doing false/early start (and if not error out).</p>

<p dir="auto">Receiving is of course not ok, but that cannot be, unless the application is receiving in parallel in two threads (which is not supported).</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/merge_requests/935#note_144761557">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/d58dea7d06d01629af7c1ca5eb58ff5c/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 Merge request","url":"https://gitlab.com/gnutls/gnutls/merge_requests/935#note_144761557"}}</script>

</p>

</div>

</body>

</html>