On Mon, Jun 1, 2009 at 10:50 PM, Darin Fisher <da...@chromium.org> wrote:
> When navigating back, we reload the page. However, we set a flag to
> indicate that cached content should always be preferred even if it is stale.
Thank you.
But what do you mean when you said "cached content should always be
preferred even if it is stale"?
Does Chrome still issue HTTP requests and check if the cache control
of HTTP response before it pull the data from content cache? If yes,
how is that 'flag' change anything?
Or how is navigating back different from load 1 page, kill the browser
(assume the page content is now saved in cache) and start the browser
again and reload the same page?
> That is consistent with all other major browsers with one
> exception: some of the other major browsers implement a page cache, which holds the DOM of
> recently visited pages in a frozen state so that they can be quickly
> restored when navigating back or forward. Such browsers behave similarly to
> Chrome when the page you are navigating back to is not found in the page
> cache.
> -Darin
>
>
> On Mon, Jun 1, 2009 at 2:23 PM, Lucius Fox <lucius.fo...@gmail.com> wrote:
>>
>> Hi,
>>
>> Lets say i have 1 tab and I load 3 sites.
>> 1. www.cnn.com
>> 2. www.yahoo.com
>> 3. www.aol.com <-- the current page
>>
>> What happens when users click 'Back'?
>> does chromium keep www.yahoo.com/www.cnn.com in memory? if yes, how
>> many pages it can keep in memory?
>> Or chromium just reload the page from scratch ? (just like user type
>> 'www.yahoo.com' again in the URL box? (and it appears faster since
>> some files (e.g. images/js files) are already in cache?
>>
>> Thank you for any explanation.
>>
>> >>
>
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
