                                                                                                                                                                                                                                                                
Received-SPF: pass (google.com: domain of erlang-questions-boun...@erlang.org designates 192.121.151.104 as permitted sender) client-ip=192.121.151.104;
Message-ID: <SNT125-W27CA183E7CE7AA0792B1869CE60@phx.gbl>
From: Matthew Evans <mattevans...@hotmail.com>
To: <erlang-questi...@erlang.org>
Date: Fri, 14 Oct 2011 21:29:04 -0400
Importance: Normal
MIME-Version: 1.0
Subject: [erlang-questions] New NIF behavior in R15???
Precedence: list
Content-Type: multipart/mixed; boundary="===============1654791848027755233=="
Errors-To: erlang-questions-boun...@erlang.org
Sender: erlang-questions-boun...@erlang.org

--===============1654791848027755233==
Content-Type: multipart/alternative;
	boundary="_38bfe028-716c-4272-9243-5f90175ce645_"

--_38bfe028-716c-4272-9243-5f90175ce645_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi

Within the next month or two we will be starting a project interfacing Erla=
ng to a C driver. This requires the use of a thread pool to support asynchr=
onous behaviors. Ordinarily I would implement this with a linked in port dr=
iver. However=2C Rickard Green at his 2011 SF Erlang conference talk indica=
ted that new support in the NIF framework might be forthcoming in R15 to su=
pport linked in driver style threading behavior in NIFS.

I would rather hold off implementing a linked in driver if the new NIF feat=
ures are around the corner. Can anyone give any hints if this will be the c=
ase?

Thanks

Matt
 		 	   		  =

--_38bfe028-716c-4272-9243-5f90175ce645_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style>
</head>
<body class=3D'hmmessage'><div dir=3D'ltr'>Hi<br><br>Within the next month =
or two we will be starting a project interfacing Erlang to a C driver. This=
 requires the use of a thread pool to support asynchronous behaviors. Ordin=
arily I would implement this with a linked in port driver. However=2C Ricka=
rd Green at his 2011 SF Erlang conference talk indicated that new support i=
n the NIF framework might be forthcoming in R15 to support linked in driver=
 style threading behavior in NIFS.<br><br>I would rather hold off implement=
ing a linked in driver if the new NIF features are around the corner. Can a=
nyone give any hints if this will be the case?<br><br>Thanks<br><br>Matt<br=
> 		 	   		  </div></body>
</html>=

--_38bfe028-716c-4272-9243-5f90175ce645_--

--===============1654791848027755233==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions

--===============1654791848027755233==--