This past week, I was chatting with my friend - and ex-boss - Chris Fuller (cfuller12) from Optaros about caching pages for authenticated users.  He'd been implementing authcache to cache pages for his latest deployment but was going to need to do some tweaking to get dynamic aspects of the page working for logged in users.  I've been busy writing proposals and keeping the Achieve-machine moving forward so the development challenge was a great reason to do something

I have been working on upgrading the caching contrib modules to Drupal 6 and started to notice some patterns and duplicated code, which led me to think Drupal's approach to caching in general. We currently have a fairly limited API for caching, but we have a magic bullet that helps us overcome some of these weaknesses: the cache.inc override system. Anyone who has spent time on large production sites knows that one of the easiest ways to see better performance on your Drupal system is to use one of the existing cache mechanisms that I spoke about at Drupalcon Boston.