[development] Static Page Caching

Joe Stewart joe at openconcept.ca
Tue Jan 10 20:11:30 UTC 2006

on 01/10/2006 01:44 PM andre said the following:
> Darrel O'Pry wrote:
>>Blocks and  menus can present a challenge... what about a lightweight
>>blocks.php and menus.php.  use ajax or SSI's to load them into cached
>>pages? microcontent servers.
> Well in my books cache never means 'cache forever.'  Therefore blocks 
> and menus are fine - if there is some latency its not the end of the 
> world for most people...  But - a few must have features are:
> -static page cache 'time to live' setting
> -manual 'rebuild' static page cache button of some sort
> -theme change detection to 'urge' admins to update their static page cache
> -setting for hook_cron - i.e. rebuild none/some/all static page cache 
> items every so often

Yes, there would be a need for cron job to help with garbage collection 
in the event that no php pages were called.  Otherwise whenever 
cacheable php pages are called, the garbage collection at least has a 
possibility of being run.

building a static site completely is one method cms' use to deploy sites 
for production.  Another is to build the cache as the files are 
requested.  This is the method proposed.

For completeness hooks for jpcache to do the things above and mentioned 
earlier are here:


The method linked at the jpcache site for integrating jpcache misses any 
control other than cache expire time.

But I want to be clear.  I am not tied to jpcache.  The internal cache 
mechanism could be expanded.  We are interested in gauging the interest, 
whether existing methods were preferred, etc.  Also whether the anon 
cache would be better moved into a more robust cache module.


> andre
> ___________________________________________________________ 
> Yahoo! Photos – NEW, now offering a quality print service from just 8p a photo http://uk.photos.yahoo.com

More information about the development mailing list