[erlang-questions] Windows Pipes as erlang network transport.

[Jeffrey Rennie]

Sewer is an experiment to use Windows Pipes instead of sockets as the
transport for erlang messaging.  The current code proves the concept.  It
plays a game of hot potato using either erlang's native sockets or Windows
Pipes.

Why would anyone want Windows Pipes instead of sockets?
1.  Running in an enterprise environment where Erlang's cookie's do not
integrate with existing authentication and security.
2.  Want to run on a user's machine, and don't want the Firewall warning to
pop up.  The user may not even have permission to poke a hole in the
firewall.

Please give it a try:
https://github.com/surferjeff/sewer

Does this look useful to anyone?  What kind of license would best work with
existing Erlang users?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20141223/0f42a139/attachment.htm>