I have an application that uses the v8 to run concurrent script jobs using multiple v8 isolates. There is a desire to move this application to Node.js, which puts the v8 used by the application in conflict with how Node.js uses its instance of the v8 (e.g. the v8 platform isn't exposed outside Node.js, etc).
So, the question is, if I build the v8 as a static library and link it into the application, so it has its own globals, etc, will it still conflict with the instance of the v8 loaded by Node.js? I am thinking of any Windows global atom names, any names used within the v8 derived from the process ID (e.g. named mutexes, shared memory, etc) and so on. Application threads making calls into the static instance of the v8 will never cross into the Node.js v8 instance and vice versa, so if there is any thread local storage used allocated in any of the v8 calls, it should not cause any mix-up with TLS values. Likewise, any handles allocated in one v8 instance will never make it into calls against another v8 instance. From the programmatic point of view both v8 instances are completely separated. I'm only worried about is any system resources that can be accessed via some OS mechanisms, like those mentioned above. Any thoughts on this would be greatly appreciated. Thanks. -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
