On 5/19/11 9:16 AM, Jay Garcia wrote: > On 19.05.2011 10:33, David E. Ross wrote: > > --- Original Message --- > >> On 5/19/11 8:18 AM, Jay Garcia wrote: >>> On 19.05.2011 08:51, Rick Merrill wrote: >>> >>> --- Original Message --- >>> >>>> How can you tell if a site you frequent >>>> is setup to use prefetch of web pages? >>>> >>>> >>> >>> I think you're confusing prefetch with "cache". There is no prefetch as >>> such for web pages. >>> >>> To find your cache entries in SM, enter about:cache in the URL location >>> window and then under Disk Cache Device, click the link "List Cache >>> Entries" - a list of all cached sites,etc. will be displayed. >>> >> >> No prefetch? On the SeaMonkey menu bar, go to [Edit > Preferences]. On >> the Preferences window, select [Advanced > Cache] under Category (left >> pane). On the bottom of the Cache pane is a checkbox to enable >> prefetching. >> >> See <https://developer.mozilla.org/en/Link_prefetching_FAQ>. >> > > From the FAQ: > > "When the user visits one of the prefetched documents, it can be served > up quickly out of the browser's cache" .. Note: cache :-) > > With today's connection speeds, CPU and RAM speeds, I see no advantages > to what they call "prefetch", same theory basically as Windows PreFetch > which IMHO is useless. > > They're also referencing an outdated http/1.1 spec as well. >
Obviously, prefetching would not cause a Web page to appear in a user's browser before the user requests it. The prefectched page does come from the cache, but it went into the cache by being prefetched from the Web before the user requested it. -- David E. Ross <http://www.rossde.com/> On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
