Re: lynx-dev Why doesn't lynx cache HTML source?

[David Combs]

Not flaming you.  Just the arguments that I keep hearing over
and over -- make lynx smaller, smaller, smaller.

And truly I know nothing about caching, or about the difficulties
with it, but really dislike the waiting when I back up on the stack
to re-download something I might likely not want to see at all!

Certainly there could be options on max bytes to save on disk
(of course it would be saved to disk, not in core, huh?),
and some lru toss-away rule depending on that option,
and maybe a settable time-limit for cache to stay (with maybe
optional prompt  "file expired -- want to keep anyway?"),
etc.

It would have to be run-time turn-on-offable, so the user could
determine whether he wanted a simple and at times incorrect
caching, vs no caching at all.  His choice -- likely made 
differently at different times.

I would say that also for this session only, and for only
this run of lynx -- no second person running lynx could
use "my" cache.

Maybe it can be simplified enough (by restricting what it does),
and optional enough, to be useful to most of us most of the time.

THAT would be a win.

Again, was not intending a flame, though that's what it came out
as.  Sorry.

David