Webpages and their components are usually cached both to memory (for fast reaccess in the current browser session) and hard-disk (for access in a future session). This ensures minimal bandwidth usage.
It also ensures maximal wasteage in terms of disk I/O and storage space, and high filesystem entropy
as pages are deleted and overwritten.
Suggested is a cacheing system that only stores the pages and components that are visited often enough to warrant taking up diskspace in between browser sessions.
An added user-defined parameter Days controls the lag period, and the History use is expanded to included items' metadata.
Deletion of cache items is in the same manner as usual: the items are allowed to fill the cache until a user-defined maximum cache size is reached, andor an item is actively deleted if the Days (since last access) has been reached for it.
A frequenter of the HB would hold the croissant icon, as well as the bun/bone .gifs in cache, the vain and stalkers would cache account pages;
A frequenter of a site with a massive static Flash homepage would hang onto the .html source and the Flash item;
A frequenter of an online newspaper would cache the banner, persistent advertising, and any photographs that are still there from the last visit.
(and yes, it means that a site/item has to be visited twice within the Days time-period before content is cached to disk at all)
Ask your computer-geek if Frequent Flyer Cacheing is right for you.