[erlang-questions] Do you wanna play with enif_select?

[Daniel Goertzen]

I'm excited to see progress in the area, but I am struggling to understand
a few things in the enif_select API:

1. Why are the resource extensions required? Couldn't a 'stop' message be
sent to the calling process which could then call a plain old NIF to shut
things down?

2. Does the ref parameter have to be a ref?  An arbitrary term would be
useful.

Thanks,
Dan.

On Fri, Dec 2, 2016 at 9:22 AM Sverker Eriksson <
sverker.eriksson@REDACTED> wrote:

> https://github.com/erlang/otp/pull/1264
>
>
> This PR is introducing a new feature enif_select() as a way for
> NIFs to ask for asynchronous notification when a file descriptor
> (a socket for example) is ready for (more) reading or writing.
>
> The API is not carved in stone yet and we would like some feedback.
> So please, take enif_select for a spin and share your thoughts.
>
> /Sverker, Erlang/OTP @ Ericsson
>
>
> _______________________________________________
> 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/20161207/5077ef7d/attachment.htm>