MDN/Archives/Kuma/Scripting: Difference between revisions

Line 78: Line 78:
** Embedding JS in a Python app seems experimental, and outside webdev team core-competency
** Embedding JS in a Python app seems experimental, and outside webdev team core-competency
** HTTP is a webdev core-compentency, and has loosely-coupled benefits
** HTTP is a webdev core-compentency, and has loosely-coupled benefits
* [http://nodejs.org/docs/v0.3.1/api/vm.html#vm.runInNewContext Built-in node.js sandboxing features]
* Taming semi- or untrusted JavaScript code
* [http://gf3.github.com/sandbox/ Sandbox] to wrap JS execution in node.js?
** [http://nodejs.org/docs/v0.3.1/api/vm.html#vm.runInNewContext Built-in node.js sandboxing features]
** Seems to have some more features than built-in node.js sandboxing
** [http://gf3.github.com/sandbox/ Sandbox] to wrap JS execution in node.js?
** timeouts, restricted method access, graceful errors
*** Seems to have some more features than built-in node.js sandboxing
*** timeouts, restricted method access, graceful errors
* Use standalone [https://github.com/visionmedia/ejs embedded JS templates] instead of literals embedded in script?  
* Use standalone [https://github.com/visionmedia/ejs embedded JS templates] instead of literals embedded in script?  
** Employs code-in-markup instead of markup-in-code, and avoids the need for fancy compiler hijinx
** Employs code-in-markup instead of markup-in-code, and avoids the need for fancy compiler hijinx
Confirmed users
920

edits