|
![](/i/fill.gif) |
More erlang fanning:
The protocol between the deamons:
http://www.erlang.org/doc/apps/erts/erl_dist_protocol.html
The protocol between the individual actors:
http://www.erlang.org/doc/apps/erts/erl_ext_dist.html
You want to look at 8.21 and 8.22. It seems the code doesn't ship, since
logically the function can't really be constructed at runtime. Instead, it's
a reference into the BEAM file (where a BEAM is like a java jar).
Because of course "external term format" is exactly what anyone would google
for to find that. I'm also rather amused that altho Erlang has wonderfully
powerful expressions for parsing byte streams, they used ASCII art with
ambiguous textual descriptions to describe the format of the stuff on the
wire instead of giving you the Erlang expression that would parse it
unambiguously.
--
Darren New, San Diego CA, USA (PST)
"Coding without comments is like
driving without turn signals."
Post a reply to this message
|
![](/i/fill.gif) |