On 2008.10.22., at 9:58, [EMAIL PROTECTED] wrote:
On Oct 20, 5:49 pm, Attila Szegedi <[EMAIL PROTECTED]> wrote:
On Oct 20, 2008, at 4:35 PM, [EMAIL PROTECTED] wrote:
Bit off topic, but I see work was done on Continuations in this
version. Is there any plan to make Continuations work in other
optimization levels beside interpreted as well?
You can't have continuations in non-interpreted mode without a
separate Java based Continuations solution. It might be possible to
integrate with an existing solution for continuations in Java, i.e.
RIFE, but that'd probably take a nontrivial amount of time and
effort.
Attila.
Too bad. I use Rhino inside a product where all JS code is run in
"compiled mode". I do not have the option to switch to interpreted
mode and would have liked to be able to use Continuations.
At my company, we're using Rhino in interpreted mode to run our
critical revenue generating service. It's been in production for
almost five years now, and the scalability that continuations give us
far outweighs any performance disadvantages we supposedly have by not
compiling to bytecode. We run several hundreds of thousands of long-
running script instances (each with multiple continuation suspends and
resumes) per day, and rising. There's messaging middleware that
implicitly also acts as a load balancer between the script-running
JVMs (when a continuation is ready to resume, it's shoved into a JMS
queue), so we can nicely scale out simply by adding further script
interpreter JVMs that feed off the JMS queue. We're quite happy with
this setup.
Attila.
--
weblog: http://constc.blogspot.com
twitter: http://twitter.com/szegedi
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
