4 ms·
> You're just sending text around. Unless I'm mistaken, it's using Erlang's distribution protocol, which is not 'just text'. http://erlang.org/doc/apps/erts/e
by davidw 10y ago
> You're just sending text around.
Unless I'm mistaken, it's using Erlang's distribution protocol, which is not 'just text'.
http://erlang.org/doc/apps/erts/erl_dist_protocol.html http://erlang.org/doc/apps/erts/erl_dist_protocol.html
As to whether some other form of sharing data between Ruby and Erlang is more appropriate, I'm sure it depends entirely on the application. At $current_job - 1 we used the Java/Erlang libs to let Android and Erlang talk, and it worked pretty well. We did not need other systems to access the same data, or the additional overhead an extra piece of software would have required.
- poorman 10y agoAh, I see this now: https://github.com/KDr2/erlix#about-the-class-erlixmessage https://github.com/KDr2/erlix#about-the-class-erlixmessage. So I guess it is handling encoding. P.S. zeromq doesn't require you to run another system, it's just a lib.
- davidw 10y agoWell, yeah, 'just' an extra lib with its own encoding and decoding. If your system as a whole revolves around Erlang, it's a fine choice for a protocol. Other times, something more 'standard' that lots of disparate pieces can talk to is better. Totally something to be decided by whoever is building it.
- vertex-four 10y agoWhile it's just a lib, it does implement an alternative networking system to the one you're using everywhere else in Erlang, which requires different ways of interacting with it and different knowledge of all the fun edge cases.