<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello Bernd,</p>
<p>thank you for your answer. I agree that it is logical that
non-blocking operation refers only to the actual socket operation.
<br>
</p>
<p>I guess that I missed the fact that InetSocketAddress is the
actual object doing the actual name resolution and therefore I can
do it separately.</p>
<p>Best regards<br>
</p>
<p>Didac V.<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 18/09/2023 23:28, Bernd wrote:<br>
</div>
<blockquote type="cite"
cite="mid:29D54560-9D50-014B-9760-BDB3599979CC@hxcore.ol">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div> </div>
<div>
<div>
<div>The non-blocking refers only to socket operations,
resolving the address is logically outside (it helps to
think about C API I guess where the connect gets a
resolved address). If you want to async resolve the
address you would have to do that separetly (or do it in
its own thread since async resolvers are tricky)</div>
<div id="ms-outlook-mobile-signature">
<div><br>
</div>
<div dir="ltr">Gruss</div>
<div dir="ltr">Bernd</div>
<div style="direction:ltr">-- </div>
<div style="direction:ltr"><a class="moz-txt-link-freetext" href="http://bernd.eckenfels.net">http://bernd.eckenfels.net</a></div>
</div>
</div>
<div> </div>
<hr style="display:inline-block;width:98%" tabindex="-1"><br>
</div>
</div>
</blockquote>
</body>
</html>