MozillaZine

Full Article Attached Feature Status Update

Thursday March 29th, 2001

James Russell has volunteered to pick up the Feature Status Updates from Gerv. This is the first of many from James, with updates on imglib2, View Manager 3, the Cache rewrite, and many others. Click the Full Article link to check them out.

If you have a feature update, or a feature you think is missing, e-mail James (only features included in the Mozilla tree itself will be considered for mention). James has agreed to post new feature status updates for every point release of Mozilla (so the next ones will be for 0.9, 0.9.1 if there is one, and so on), which should work out to every five weeks or so, given the new Mozilla roadmap.

Also, thanks to all who volunteered to take this, your support was greatly appreciated!


#11 late update about libpr0n

by Kovu <Kovu401@netscape.net>

Thursday March 29th, 2001 8:41 PM

You are replying to this message

(Initially accidentally posted in an obscure reply above)

This just in from Netscape's Gordon Sheridan re libpr0n:

"...I've asked Gagan about pushing our design docs out to mozilla.org, and he's working on it. We've landed the cache, and HTTP is using it. libpr0n is using it on whatever platforms it has been switched on. FTP was using it, and then stopped; I'm not sure if DougT has turned it back on yet. We still waiting for IMAP to transition to the new cache. Once that's done, we'll remove the old cache from the build.

"The disk cache is currently what we are referring to as "Level 0"; it's functional (or supposed to be) but has known performance issues. We are working on Level 1, which will provide dynamic eviction (Level 0 evicts only on shutdown) and efficient cache miss detection. We hope to land Level 1 by early next week. Level 2 will provide a more efficient mechanism for storing the cache entry and metadata. We hope to finish that about a week after Level 1. Level 3 will build on Level 2 and provide a more efficient mechanism for storing the data portion of cache entries.

"We are currently distinguishing new cache bugs from old cache bugs by adding '[cache]' to the status whiteboard field, so you can search bugzilla to see what's happening."