[erlang-questions] Erlang OTP 22.0-rc1 is available for testing!

Andreas Schultz andreas.schultz@REDACTED
Thu Feb 28 13:05:49 CET 2019

Henrik Nord X <henrik.x.nord@REDACTED> schrieb am Mi., 27. Feb. 2019 um
13:22 Uhr:

> OTP 22 Release Candidate 1

>    - A new (still experimental) module socket is introduced. It is
>    implemented as a NIF and the idea is that it shall be as "close as
>    possible" to the OS level socket interface.
Is a {active, N} like delivery of data planed or will polling the recv
methods be the only way the receive data? What about non-blocking connect
and accept?

My preference would be to get an active notification when data is available
for receive and another one when when a non-blocking write is possible.
Sending and reception should then be left to the caller.
Same goes for non-block accept and connect. Call accept/connect with a
async option and get some message when the procedures finishes.

Dipl.-Inform. Andreas Schultz

----------------------- enabling your networks ----------------------
Travelping GmbH                     Phone:  +49-391-81 90 99 0
Roentgenstr. 13                     Fax:    +49-391-81 90 99 299
39108 Magdeburg                     Email:  info@REDACTED
GERMANY                             Web:    http://www.travelping.com

Company Registration: Amtsgericht Stendal        Reg No.:   HRB 10578
Geschaeftsfuehrer: Holger Winkelmann          VAT ID No.: DE236673780
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20190228/99db7908/attachment.htm>

More information about the erlang-questions mailing list