erlang/python,ruby,.. interfaces on tcp
Mon Aug 10 10:42:45 CEST 2009
an old question here: i'd like to interface erlang with python, ruby, and
other languages as i go. i am aware of the existance of port drivers
. you need to develop one for each erlang / other language couple;
. a crash in the port driver brings the emulator down too.
therefore, i'm thinking to use a binary protocol over tcp/ip. this allows:
. to have only a single exit/entry point from erlang structured as a tcp
. to avoid crashing the emulator if something goes wrong in the client.
since communication between erlang nodes is done by tcp, i think this could
be an interesting thing to try out.
1. do you think that this is worth a try, or you'd better really be off with
port drivers? i know there's one for ruby
http://github.com/mojombo/erlectricity/tree/master for instance.
2. what kind of fast binary protocol would you recommend?
More information about the erlang-questions