On Jan 20, 10:59 am, Patrick Dobbs <[email protected]> wrote: > Hi, > > I'm hoping for some clarification. In common with a lot of projects that > seem to be cropping up in this newsgroup, I've got a rhino shell session > starting up a webserver and then registering a javascript handler for > http requests. > > However, a shell session presumably creates one Rhino Context. And there > can only be one Thread per Context (or vice versa). So what happens when > a Rhino Shell session (single threaded) starts up a multithreaded web > server, and that webserver then calls into Rhino? > > I'm assuming that this model (Rhino script invoking its own webserver) > is inappropriate for production environments for this reason, and I'm > planning on only using this mode for development. However, I would like > to improve my understanding of this situation. > > Thanks > > Patrick
The typical model is for each request in the web server to enter a Context and then execute a script. This way you can have multiple requests being processed concurrently in different threads. --N _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
