ManilaFixer TurboCache

This part of manilaFixer creates a message based cache for your website. The cache writes to the discussion group storage, which is in the website root. No patches to Userland scripts are required, although turning the cache on does patch some key scripts in your Manila website. Turning it off comments out the changes.

This cache is enabled on a site by site basis. Hit statistics are maintained automatically and visible through the plug-in. There is a way to flush all cached messages. There is a way for other plug-ins to register a cache callback and to override a decision to use a cached page.

The effectiveness of any cache varies with the cost of building the pages every time they are used. For complex pages we have seen greater than ten-fold improvements in response time. The trade-off is the increased use of memory because Frontier never pages out memory that it has loaded from the Object database.

Gotcha number one! Editors don't see cached pages! Editors don't see cached pages!

Why don't editors see pages from the cache? Because they are the only users who see the editors only menu and its probably not worth caching pages with the menu.