Re: address@hidden: lynx-dev caching after \ (was why reload etc?)]

[Nelson Henry Eric]

> having to re-retrieve the page.  I would want Lynx to use the same
> algorithms it uses for caching rendered pages.  I would want to have the
> option of telling it to cache *both* rendered and raw pages, to cache
> only rendered pages (as it does now), or to cache only HTML source.  The
[...]
> finds the raw page, so it gets re-rendered from memory.

All of this sounds good, especially the part about having various options.

The one problem I have is that with the antiquated hardware I have, memory
management is VERY poor; the cache would have to be on disk for me or my
users to make use of it.

> see the source for that link.  Now hit left-arrow to go back to the main
> page.  Now follow the first link.  You get the cached *source* page
> rather than a rendered page.  For the parallel-caching model to work,

Is that really a *source* page, or is it a _rendered_ version of the
source?  What I see on the screen is all lines cut off at 80 characters,
so I question if it is _raw_ source as one would get by d)ownloading.

> Lynx needs to have a set of flags associated with cached rendered pages,
> telling it under what conditions this rendering is valid (and thus,
> under what conditions it needs to re-render it, either from cached
> source or by re-fetching that source).

Exactly.  (Seems to add a lot of complexity.)

__Henry