I tried to do the same a while ago. Correct me if I'm wrong, but I believe v8 uses thread local storage in some specific parts of its implementations. This would have to be replaced with fiber local storage in order for v8 to work properly in the presence of fibers.
On Fri, Aug 20, 2010 at 12:38 AM, malcolm handley <[email protected] > wrote: > I'm looking into adding to v8 support for fibers or cooperatively > scheduled threads. I've read a bunch of posts on v8 and threading so > far and my understanding is that it's ok to have multiple threads > executing v8 code as long as they hold V8::Locker when they do so > (and, hence, that only one of them is executing v8 code at a time). > > Is this correct? Are there any pitfalls I should be aware of or > reasons that this is a non-starter? > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
