I think the file transport needs to make use of the memory cache before hitting up the disk for the file in question. The nsIChannel::FORCE_RELOAD flag should be hooked up to bypass the memory cache too.

Marking beta2.

m16

Moving to M17 which is now considered part of beta2.

As I think about this, it probably should only be done for the resource: protocol. That way things like the throbber images come out of the memory cache, but not arbitrary files that are being accessed. The FORCE_RELOAD stuff is still needed. Changing summary from "file transport needs to use memory cache" to "resource: protocol needs to use memory cache". Also I don't think this is a beta2 requirement -- it's a perf thing.

stop the spam

David has left netscape and davidm@netscape.com is an invalid email address. Assigning his five remaining bugs to gagan to find a new owner for them. Thanks

oops i didn't actually reassign to gagan last time. sorry for the spam

dawn: neeti is our cache incharge now.

warren: what do you feel about this? (I would let you make the call on the nomination for this)

I think the file: protocol (used by resource:) should be augmented to use the memory cache -- if for no other reason than to allow imagelib to cache the throbber images. I think that's the best solution for it since it holds the image in memory in a compressed format -- saves space and time. Marking nsbeta3+.

Throbber images should come from imgcache. Let me talk to Pam before I close this out if that the case.

dp: I'm working on putting chrome animations in the image cache as we speak. -p

--> Pam

....annnnnd its a dupe of 41268. *** This bug has been marked as a duplicate of 41268 ***

verif. dup