<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>Right,<br><br>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.<br><br>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.<br><br>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).<br><br>Matt<br><br><hr>Date: Sat, 15 Oct 2011 19:37:44 +0100<br>Subject: Re: [erlang-questions] New NIF behavior in R15???<br>From: watson.timothy@gmail.com<br>To: mattevans123@hotmail.com<br>CC: joelr1@gmail.com; erlang-questions@erlang.org<br><br><div class="ecxgmail_quote">On 15 October 2011 14:45, Matthew Evans <span dir=ltr><<a href="mailto:mattevans123@hotmail.com">mattevans123@hotmail.com</a>></span> wrote: </div><div class="ecxgmail_quote"><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex">
<div><div dir=ltr>From what I understand the new NIF features are intended to supercede the use of linked in drivers.<br><br></div></div></blockquote><div><br></div><div>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. </div>
</div>
</div></body>
</html>