At Sun, 27 Nov 2011 11:29:11 +0100, Roeder, Marko wrote: > > On Nov 27, 2011, at 8:19 , Yoshiki Ohshima wrote: > > One more bit of trick I can think of is to run another JavaScript > environment in NaCl; the upside of this would be to have a completely > separated address space for your program. Lively Kernel currently > seemingly does a good job of not hard-crashing easily even when the > programmer is trying self-rewriting code. But if such code is > literally isolated in another address space, it would be much safer to > experiment. (Though most of this safely can be provided by browser > tabs.) > > There is already a way to safely run (unknown) JS code in a sandbox-like > environment on your web page. I have looked into this the last couple of days > and (web) workers (HTML 5) seem to do a > great job and are available not only in Chrome (as NaCI is). > One example is https://github.com/eligrey/jsandbox. But I am sure there are > more implementations for that.
Ah ha, thanks for the info. If it could be changed to support the "delayed inheritance" that "Worlds" would do (namely, some disiplined way to share values; that would require to translate the variable accesses to some code that asks the values from the master), that would be perfect. -- Yoshiki _______________________________________________ lively-kernel mailing list [email protected] http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
