Good points. Thank you for all the replies. I believe js run in similar execution paths for each machine/use case.
can we get the statistical information on the server about the most common execution trace of the JS, analyze it and just transmit the top a few possible binaries to "computer B"? so it will be likely to receive the binaries needed from cloud (and fallback to local JIT when type prediction miss) yeah, I agree transmitting binary code is dangerous -- but verifying it is in fact easy, just deploy the JS-to-binary in trustable machine and also check CRC32 will ensure the code's integrity? Is it still too costly? On Aug 24, 7:44 pm, Chris Angelico <[email protected]> wrote: > On Thu, Aug 25, 2011 at 4:02 AM, Ligon Liu <[email protected]> wrote: > > I'm a total newbie to V8 but I have a question: after javascript is > > compiled to binary code in memory by the v8 engine at "computer A", is > > there any way to separate the binary code into a file and transmit it > > to another "computer B" with v8 engine and execute the code on > > "computer B"? > > As well as what Jakob has said, such a scheme would raise major trust > issues. You would be transmitting compiled code across the internet - > have you any protection against malicious or damaged code? If not, > you're majorly at risk; if so, the protection probably costs as much > processing (and therefore power) as the compilation would have. > > ChrisA -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
