[wp-hackers] Caching as part of the core

[Mike Schinkel]

On Jul 21, 2012, at 8:56 PM, John Blackbourn <johnbillion+wp at gmail.com> wrote:
> If there were a fragment caching API, the only difference in this bit
> of code would be the name of the functions used to retrieve and store
> the fragment. 

Actually, no.  A fragment caching API would benefit from numerous potential criteria that can select or invalidate the cache such as current time, current $post->ID, if the current page us an archive page or and is so what type, and a whole lot more. 

Clearly a fragment cache can be developed using an object cache but it takes time and experience to determine what fragment-specific features are needed and what architectures work the best. And that's exactly what a community of open-source developers is better at than a single developer hence why adding such an API to core as well as other caching APIs would be beneficial. IMO.

-Mike