DevShed has the latest article posted in their "Caching Result Sets in PHP" series today - A Content-Change Triggered Caching System.

Welcome to the second part of the series "Caching result sets in PHP." Over the first part of the series, we discussed the benefits of having a result set caching system working on the backend, as an efficient mechanism to reduce the overhead caused to the server, particularly when it’s serving many requests from a database-driven application.

Due mainly to the flexible nature of the generated source code, in this second part, we’ll take a look at an application that triggers the caching mechanism based on a content change condition, without modifying its core logic.

They look back at the old script and give tons of ways to improve it. As they mentioned, making it more modular only helps to make the caching easier (and usually faster) down the road...