Comment #28 on issue 235 by ryan.gahl: Support the Javascript E4X extension http://code.google.com/p/v8/issues/detail?id=235
In the mean-time, Jaxer (jaxer.org) is based on spidermonkey, and could be used in a nice little "nginx > node.js > jaxer" configuration in order to get the awesomeness that is E4X in your stack today. I'm playing with a prototype framework with that signature and I think it's a fairly sound architecture. nginx to serve&cache static content + reverse proxy to node.js, which handles most of the processing stuff but proxies down 1 more layer to jaxer when initial page/widget templates need to be created (so node then acts as a cache layer for the nice E4X genned stuff as well).
Since node's #1 rule is "thou shalt not perform blocking operations"... async proxying to jaxer for the initial template rendering is a nice way to do it, IMHO. The same technique could be used for E4X use cases other than templating, as well.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
