[erlang-questions] New NIF behavior in R15???
Mon Oct 17 13:43:48 CEST 2011
In my case I have C code (drivers and an api to some hardware), Java code (some app logic and an ipc to a larger java app) and some Erlang doing ipc and running a pattern matching app.
What would be nice with the new NIFS is to build the C code as a collection of NIF processes, use Jinterface for Java; effectively giving the ability to split processing into "applets" all communicating via erlang ipc. The java apps could talk to the C code via an erlang message directly, we could then move work from java to erlang or visa versa.
I can do this now using NIFS or linked-in drivers and an erlang middleman process, but the ability to do it directly is compelling (I.e. Java to a C NIF directly using erlang ipc as opposed to Java to Erlang process to C).
Date: Sat, 15 Oct 2011 19:37:44 +0100
Subject: Re: [erlang-questions] New NIF behavior in R15???
On 15 October 2011 14:45, Matthew Evans <> wrote:
>From what I understand the new NIF features are intended to supercede the use of linked in drivers.
Right, I apologize for the confusion. This is exactly what I was talking about - on slide deck he calls them "Native Processes" - I had forgotten that the enhancements were going to sit along side the existing NIF APIs as it's been quite some time since I saw the presentation online.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions