Other then search engines what type of sites gain any benefit from this?
For external links, if you aren't a search engine, you don't know what resources need to be prefetched and even if you did you will have no way of knowing when it changes (other then manually).
For internal links, in most cases the resources are already cached and http 2.0 server push is going to fix the rest.
Beyond that, the API looks clunky - instead of having a "prefetch" attribute on a link, you need to add more links with special syntax to the header dynamically.
What's the point in adding this functionality to a browser? this looks like an implementation specifically designed to make only google search faster.
Comments
Other then search engines what type of sites gain any benefit from this?
For external links, if you aren't a search engine, you don't know what resources need to be prefetched and even if you did you will have no way of knowing when it changes (other then manually). For internal links, in most cases the resources are already cached and http 2.0 server push is going to fix the rest.
Beyond that, the API looks clunky - instead of having a "prefetch" attribute on a link, you need to add more links with special syntax to the header dynamically.
What's the point in adding this functionality to a browser? this looks like an implementation specifically designed to make only google search faster.
you could find out if google set up an API that exposed this information. Then a simple plugin could update the links on your page.