Darin Fisher wrote:
> 
> The new cache branch has now been merged onto the mozilla trunk.  It is,
> however, still disabled by default.

Does the new cache address
http://bugzilla.mozilla.org/show_bug.cgi?id=40867 at all? Make it easier
to address in future?

Knowing the apalling state of View Source right now, I had assumed that
this would be one of the main issues that needed to be fixed by an
enhanced cache (the ability to get back an accurate copy of the source
of whatever page I am *actually* viewing, regardless of whether it was a
form post or set caching off, and to save that page to disk).

However there don't seem to be many comments in the bug related to the
new cache and certainly nothing in there to indicate that it will be
fixed by the new cache. It seems a shame for a major correctness,
mostfreq and dataloss bug
(http://bugzilla.mozilla.org/show_bug.cgi?id=55583 is blocked by it and
is mostfreq) not to be addressed by a rewrite of the component it's
in...

I'm not intending to sound at all ungrateful for all your hard work - I
know that a lot of other major issues are addressed by the cache
rewrite. Just evangelizing one of my biggest pet peeves with Mozilla
right now...

Thanks,
Stuart.

-- 
Stuart Ballard
Programmer
NetReach, Inc.: Single-Source Provider of Internet Solutions
One eCommerce Plaza
124 South Maple Street
Ambler, PA 19002
215.283-2300, x126
www.netreach.net
[EMAIL PROTECTED]

Reply via email to