Communication with existing non-Erlang processes ?

[Scott Lystig Fritchie]

>>>>> "rn" == Raimo Niskanen <raimo@REDACTED> writes:

rn> The entusiastic user may write a linked-in driver that handles
rn> named pipes, which probably is the way we will have to do it.

Those who are interested in a tremendously-ugly-but-it-works-anyway
modification of the inet driver to support UNIX domain sockets should
look in the User Contributions section for the "unixdom" package:
http://www.erlang.org/user.html#unixdom-0.1.

I apologize for not maintaining it beyond it's current state, but it
really does work.  If it would be a useful starting point for named
pipe work, or merely an example of what can be ripped out of the TCP
part of the inet driver by someone who barely knows what he's doing,
be my guest!  :-)

-Scott