On Sat, Aug 1, 2015 at 4:22 AM, SubProtocol <[email protected]> wrote: > I'd like to add v8 to a project I'm working on. It uses a library that > controls the thread creation though, so I'm not sure how this complicates > things for me. > > The threads don't cross-communicate or share any data between them. All I > want to use v8 for is to take a std::string, transform it in some way, place > the result back into a std::string. I'm thinking I can possibly do this if > I create a wrapper class for all the v8 isolate + initialization code, and > then use boost::thread_specific_ptr to (if it hasn't been done yet) create > the object for each thread, which essentially initializes a threads v8 usage > for the duration of the threads life. > > Does what I describe sound practical? > > > Also, my understanding is that an Isolate is essentially a single-threaded > instance of the VM, but you can still run one Isolate per thread so that you > can saturate cores with parallel execution? > > Please let me know if I am off base. > > Cheers, > > SubProtocol
Sounds about right. The only thing to keep in mind (and only when you move an v8::Isolate from one thread to another) is to use v8::Locker and v8::Unlocker instances in the right places. -- -- 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/d/optout.
