[erlang-questions] OTP 22 socket module

Andreas Schultz andreas.schultz@REDACTED
Wed Mar 27 08:20:15 CET 2019


Is a {active, N} like delivery of data planed for the new socket 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.

I do realize that all this could be build with a gen_server/gen_statem
around socket, so I guess the real question is does it make sense to start
build such a wrapper or are the plans to make async functions part of the
socket module?

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/20190327/650672ba/attachment.htm>

More information about the erlang-questions mailing list