> (I had to use locker because in the app does initialization and code loading on a different thread that uses locker)
I dont know how you designed, but when i face a case where i need to sync with a 'v8 thread', first i always dispatch work to that thread and use some thread synchro, where the frontend thread waits for a signaling from the thread dealing with v8. I have this special treatment when dealing with shutdown.. i block the thread dealing with the main shutdown, until the thread dealing with v8 does the cleanup and signals when its done.. I also do this also when i need to dispatch some computation on v8, where the frontend thread needs to hand back a answer. I just need to make sure the thread waiting for the v8 thread will not block the whole application (its not main) or some other part that need to work independent and in a async matter. For pratical matters, when the frontend waits for the backend, its basically getting back to a fancy sync mode using two threads, but at least this way you provide a lock-free env to the v8 isolate. (also you can scale by adding more isolates/v8 threads that can be used for dispatching when theres a need) I dont know if this would work fine for your needs, but just in case it can be of some help to you.. Glad my hunch was right and that it works for you. -- -- 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.
