4 ms·
allowing a web client to become a node in an Erlang process network, and have arbitrary code pushed to and executed on it by the network Does this sound scary
by andrewflnr 15y ago
allowing a web client to become a node in an Erlang process network, and have arbitrary code pushed to and executed on it by the network
Does this sound scary to anyone else?
- derefr 15y agoWe already have arbitrary code pushed to us and executed in our browsers all the time--it's called Javascript (and with JSONP, we even have more Javascript being pushed to us in realtime in response to events and eval'ed live. Nothing new here.) The difference in running Erlang here is simply that the browser would be joining a network of agents and spawning agents of its own, instead of joining a network of processes and spawning threads/web-workers of its own. This would allow a uniformity of process logic, such that an agent could be transparently running on a browser or on a server to complete a task, and messages could be being passed transparently across the network to facilitate this, without any of the code having to differentiate the cases. NaCl ensures the browser sandbox environment remains in place--so, other than perhaps getting a bit hot, your computer won't be doing anything it wasn't already doing just running the Javascript the server served it.
- tomjen3 15y agoNot if you know how NaCL works.
- obtu 15y agoarbitrary code For certain values of arbitrary; actually the code is restricted to the NaCl sandbox and the Pepper API.