<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 09/03/2019 09:35, Andi Mullaraj wrote:<br>
<blockquote type="cite"
cite="mid:CADvBZ+1NwvWsVC6qx_Ovk+FZKRb9cUi-BuCjyeRpjm8iiEsYbQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr"><span class="gmail-im" style="color:rgb(80,0,80)">
<div dir="ltr"><br>
</div>
</span>
<div>In light of the previous point, I couldn't disagree more.
As it is painfully clear, the proposed approach stays within
the confines of nio, and no duplication is needed (I also hate
duplication).</div>
<br>
</div>
</blockquote>
This is a topic that was explored, and ruled out, in JSR-51 but lead
to SSLEngine. Yes, SSLEngine has pain points and performance issues
and I think it would be better to focus on those issues and see how
SSLEngine could be improved. This would be more beneficial for the
eco system today as most developers don't use SocketChannels or
Selectors directly (those APIs tend to be hidden by libraries and
frameworks so most developers don't see them).<br>
<br>
Also as a reminder is that we are exploring, in Project Loom, ways
to make it easy to develop simple blocking code that scales as well
as code forced to asynchronous frameworks today. If we get that
right then it should eliminate many of the reasons to create further
asynchronous or non-blocking APIs.<br>
<br>
-Alan<br>
</body>
</html>