Re: [tlug] Browser blues

["Lyle (Hiroshi) Saxon" <ronfaxon@example.com>]

Josh Glover wrote:

>Caching is a hard problem to solve, so I would not be surprised if
>there remain bugs in even Mozilla's implementation (which has been
>tested heavily for years by people like you and me). However, Mozilla's
>caching is complicated, and you may have been seeing correct behaviour
>WRT how Mozilla was configured.
>[snip]
>
>"Compare the page in the cache to the page on the network:
> 1. Every time I view the page
> 2. When the page is out of date
> 3. Once per session
> 4. Never"
>
>  
>
First - thank you for the detailed reply and code information.  I've 
saved the file for future reference.  In the meantime, I've checked the 
settings under Mozilla (I use both Mozilla and Firefox 
simultaneously...), and see that it's now set as follows:

Compare the page in the cache to the page on the network:

    Every time I view the page
x  When the page is out of date
    Once per session
    Never

- and, the following is also activated:

"Prefetch web pages when idle, so that links in web pages designed for 
prefetching can load faster."

Now I know how to get around the problem (reload), it's not a big issue 
for me, but how does the browser determine when something is out of date 
anyway?  The link I was checking was very definitely out of date, and 
yet it very persistently keep pulling the old version out of cache.....

Another question - when running Mozilla and Firefox simultaneously, is 
there any influence of one on the other, or do they run totally 
independent of each other?  Under MicroMuck, setting changes in either 
Netscape or Mozilla directly affected each other....