Gordon Mohr (@ Bitzi) wrote:
So the effect of caching was almost exactly opposite from what I expected: reloads showed no evidence of caching; accesses after user login/logout (when presumably material might have to be reparsed) showed evidence of caching.
Can you speak any more about why it might be behaving this way?
It's hard to say for sure without more information (eg a code sample) but note that in most browsers, the 'refresh' button still works in concert with client-side caching.
The browser will send an 'If-Modified-Since' header, and if the page hasn't been modified and the login session status hasn't changed the server will likely return with a '304 Not Modified' status code, so the browser will show the locally cached HTML from the last time it loaded the page.
(I'm also trying your 'might work' approach of stuffing the extra data into the ParserOutput object, but that too is working only intermittently -- again logins/logouts somehow trigger a path where the necessary info isn't retained.)
Don't forget to if necessary modify the options cache hash (in User somewhere) if it'll be different for each user. And of course, clear out old cache entries while you're debugging!
-- brion vibber (brion @ pobox.com)