Re: Efficiency of context-per-thread on shared engine vs. engine + context per thread?

From basic experience I found that using a single engine, using JavaScript code to create the new threads and using loadWithNewGlobal to start each thread gave the best overall performance. - Jim > On Feb 27, 2017, at 7:58 AM, Frantzius, Jörg > wrote: > > Hi, >

Efficiency of context-per-thread on shared engine vs. engine + context per thread?

Hi, for our application we’re about to implement a global-per-thread on single engine approach, and I’d be very thankful if someone in the know could share some insights on whether this is worth the effort when compared to engine-per thread (as the latter seems much more easy to implement for

Re: Getting Input From User

That is true. Writing a function was always an option, but ScriptContext's setReader(Reader) method made me think that there would be a way to use it like the writer. But I guess it all makes sense now. Thanks to both of you for your help. Burak On 2/27/17, Sundararajan Athijegannathan