On Wed, Oct 06, 2004 at 09:37:48AM -0400, Jorge Arellano Cid wrote:
It'd be good to have a way to control caching. Unfortunately not for the next release. It has its complexities that need careful design and time.
We're sorting a large task list by priorities now with Sebastian. I'd say in advance we'd need a volunteer developer to look on this topic. We're far surpassed by the amount of work.
ok, i will volunteer to do the caching portion. i need to finish reading Cache.txt and pick through capi.c and cache.c a bit more, but before i know everything i should know, here is what i'm planning so far: we go into cache.c as normal, if the page isn't cache, we initiate the connection and cache the page as normal. the only difference is now we search the header for the Pragma: no-cache meta tag. if we find it, we set a flag (i'm assuming Url->flags is a vector?) in the cache entry. the next time we go to that page, since it's in the cache, the first thing we check is for that no-cache flag. if it exists, we look at nocacherc (which will be structured exactly like cookiesrc) and if we have an ACCEPT match there, we simply behave as if the item doesn't exist in cache. does this sound like the proper way to do it to you guys? also, what is the proper no-cache system to honor? the Pragma meta tag? or is there something else we should look for? i'm not completely up on my HTML standards quite yet. -brian -- "The cats tend to administer themselves, and contrary to the expected facts, the house and everything in it was installed for their benefit." -- Nic Clews