What you are describing is again not a statement of the problem in itself, but an attempt to solve something. What in detail that is, is still unclear to me. I think you are mixing up the concepts of Context and Isolate: An Isolate a concept for strictly, well, isolating several V8 instances (including the heap etc.), where by definition nothing can be shared between those instances: No ScriptData, no Script, no Value, nothing. Contexts are a weaker form of separation (within the same Isolate), basically separating the global object and code. BTW: Asking how to avoid an Isolate is a misconception, you *always* use at least one Isolate behind the scenes.
As I said above, I don't know what exactly you are trying to achieve, so I can only be guessing: If you e.g. have some JavaScript that rarely/never changes and want to run this JavaScript code from various threads, just use a single Isolate, compile your code once and run it from various threads, of course using a Locker everywhere (this is e.g. how Chrome's proxy resolver is handling PAC scripts). If the various threads shouldn't see e.g. changes to the global object from other threads in that scenario, use several contexts within that single Isolate. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
