Comment #6 on issue 13505 by [email protected]: link rel prefetching should be implemented to reduce page load latency http://code.google.com/p/chromium/issues/detail?id=13505
I'm pretty sure that recursive prefetch would be a bad idea. IF the party that suggests the prefetch thinks otherwise, it should specify the extended set of sub- resources that should be loaded. I think that currently the suggestions for prefetching via link-rel might include *only* subresources, as only cached content should be preloaded, and sometimes the top-level page is not cached (but it has a pile of cached subresources). As I understand it, this bug was intended to implement the current feature as spec'ed, and we shouldn't get diverted to building extensions until we can justify the value of this feature at all. There is ongoing debate about whether the server is even qualified to suggest what should be preloaded, as it may not understand the network environment of the client. When the client is severely bandwidth constrained, pre-loading content may be a very iffy deal. We'll need some stats to quantify wins/losses before going forward. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
