Comment #4 on issue 3016 by [email protected]: Rewrite the V8 parser
http://code.google.com/p/v8/issues/detail?id=3016
but it probably covers part of your Google Search example.
It does not. The problem is that it involves cross origin navigations which
entail new renderers with completely cold caches (including all V8 caches).
I think we should come up with a scheme to allow some of this stuff to
persist across cross-origin navigations so renderers are cold less often.
Something like:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/QP9bEjbXqgs/r9NBPSfjFJMJ
I'm not sure yet how that proposal will pan out, but I'd just like to
consider in the API that Chrome or Blink may be in the best position to let
caches survive longer as well as to appropriately manage memory.
but given that we might also not use the AST format in the optimzing
compiler altogether in the long-term future
Could we just version whatever opaque data we tell the embedder to cache?
Then if V8 changes, it knows not to use it?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" 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/groups/opt_out.
