I think this is an awesome idea, especially if we make it optional through settings.php. Example - fully loaded nodes can be cached, but only if there's a node_cache specified in settings.php, so it doesn't break existing stuff (or even the content_type overrides like in advanced cache). I know it would be nice to not have to worry about patching files when a new version does come out, but that's the lazy in me talking. Josh Koenig wrote:
Greetings,
I'd like to take the community's temperature on developing a global object caching strategy for drupal core 7.0. In effect, this would mean pulling the functionality of advcache module into core, though the code would doubtless be a bit different.
This has been previously discussed by Robert Douglass and Steve Rude, and I think both the short-term and strategic value here is clear. As memcached permeates the collective consciousness of the web-development community, and as "cloud" computing becomes more and more prevalent, best practices in architecture increasingly point towards caching full objects whenever possible.
This also fits well with Drupal's existing architecture. There are great functional points (e.g. node_load()) to mount this functionality.
I'm certain I'm not the only one thinking along these lines. Anyone want to throw out their ideas?
cheers -josh