[erlang-questions] What is the point of Spawn(Node, Fun) if Node has to have the same module loadable as a client node?
Wed Sep 7 16:49:47 CEST 2016
It sounds to me as a question of authorization. Clients could potentially send arbitrary code to execute, and recipient node should be able to decide which clients are authorized for running the code on it.
On September 6, 2016 8:08:00 PM EDT, "Richard A. O'Keefe" <> wrote:
>On 6/09/16 5:23 PM, Alex Arnon wrote:
>> Would an Erlang AST do it?
>You missed the point.
>We *have* an Erlang AST.
>That can, of necessity, express ANYTHING that Erlang can.
>The great benefit of a mini-language is that it CAN'T.
>In general, such a mini-language
>> is a *scrutible* data structure in which general
>> Bad Things simply aren't expressible
>Accepting code from a remote source is always a risk,
>UNLESS it is tightly constrained so that you KNOW even
>before you look that it can't be so very bad.
>For example, if you want to write some sort of
>distributed game, and have players send "scripts" for
>their pieces to a game server, you want to KNOW that
>the scripts execute in bounded time and can only do
>erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions