[erlang-questions] OTP 22 socket module

[pablo platt]

 Andreas, do you have a wrapper module or some code you can share?
I'm trying to replace a gen_udp server with the socket module.

On Fri, Mar 29, 2019 at 7:18 PM Ingela Andin <ingela.andin@REDACTED> wrote:

> Hi!
>
> Den ons 27 mars 2019 kl 08:20 skrev Andreas Schultz <
> andreas.schultz@REDACTED>:
>
>> Hi,
>>
>> 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?
>>
>>
> It is planned to have behaviours that implement the active behaviour  but
> not as part of the socket module. The socket module should be the
> primitives.
>
>
>
>> 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?
>>
>>
> Maybe Michael will have some more comments.
>
>
>
>> Thanks
>> Andreas
>> --
>> --
>> 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
>> ---------------------------------------------------------------------
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20191028/e2a0fed5/attachment.htm>