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

[dickey]

> 
> Sometimes I want to view the HTML source of a document using the "\" 
> key, and then switch back to the rendered document when I'm through, 
> or I want to switch all images to links and back again, using the "*" 
> key, or maybe I want to turn pseudo-ALTs on or off, but every time I 
> make a switch in how I view a document, the whole document has to be 
> downloaded again.  Is there a reason why it was done this way?  It 
> seems to me that caching the HTML source instead of the rendered 
> document would make more sense, and would save time when making these 
> changes on the fly.  Of course, moving between cached documents might 
> be a little slower unless they were cached both ways (source and 
> rendered), but not by much, and rendering a cached document would be 
> much faster than downloading it repeatedly.  Could someone enlighten 
> me? 

we've talked about this, tentatively decided that local caching would
be a Good Thing, but no one's worked through the details to implement
it (there's always more things to do than there's time).
  
> Chuck 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey