What I would like is, in the webserver context, ie at webserver execution speed, to compare the mod time (or existance of a static file) and a 'flag' file. I want to leverage the speed of 'up to date' static pages, but to be able to regenerate 'old' or missing pages from database content using scripts - at run time. The idea is that a CMS modifies an internal version of a page part (eg a title page) and, at the same time, touches some 'well known' filename. The webserver comes along and compares the mod time of the file and the 'well known' (or 'flag') filename. If that 'flag' file is newer, then a page regeneration script is run and a redirect sent after the new version is (re)generated. A hierarchy would be good... Obviously one can do this in the FCGI entity of your choice, but that slows the whole site down. I have large sites where parts are not looked at from one month to the next, but detail changes are made to the look and feel in other parts. The sites are otherwise static - with no *runtime* dynamic content (although the actual content is operated on by the CMS and stored in databases of various kinds). Does this make sense? I know that if a .html is missing mod_rewrite can be persuaded to regenerate it, but, AFAIK there is no facility to compare the modtimes of two files in mod_rewrite.