Re: implications of preloaded script pages?
| From: | Brian Clark | Date: | Fri, 05 Jan 2001 21:42:50 +0000 |
| Subject: | Re: implications of preloaded script pages? | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-32951@lists.php.net to get a copy of this message | ||
Hello CC,
(CZ == "CC Zona") cczona@nospam.invalid writes:
CZ> The newest "pre-release" release of the iCab browser includes this
CZ> in its "new features" list:
CZ> <excerpt> " In the 'file' menu there's now a new entry
CZ> "Prefetch".
CZ> If this entry is checked, iCab does load all the links of the
CZ> currently displayed page in the background (only the HTML files,
CZ> no images). iCab starts loading the links as soon as the current
CZ> page has finished loading and stops as soon as you open a new page
CZ> (that means iCab does only load the links while iCab is idle).
CZ> This can speed up opening the links later, because the file is
CZ> probably already in the cache when you open it. " </excerpt>
CZ> Could visitors' use of such a feature affect my site adversely?
CZ> Say that they're visiting a page with links to several script
CZ> pages which modify a database in various ways; just by visiting
CZ> Page A would they be unintenionally triggering modifications by
CZ> linked Pages B, C, and D even though that was never their intent
CZ> (nor mine)? I realize browsers preload images all the time. But I
CZ> wasn't sure if this notion of preloading linked HTML was new news
CZ> or old.
They may have the sort of stopgap measure for things like that -- sort
of like search engines/spiders act when they see a ? or & in the URLs
for dynamic sites.
-Brian