[wp-hackers] Caching as part of the core

[Almog Baku]

It diffucllt to learn the developer 3rd party api.
And in common wordpress there is a lot of 3rd party themes and plugins.

בתאריך יום ראשון, 22 ביולי 2012, Chason Chaffin כתב:

> While I agree that fragment caching would be useful, it sounds like
> something that would be better as a plugin, since generalizing it would be
> a difficult problem, and I'd rather see how it works before adding more
> features into core.
>
> Sent from my iPhone
>
> On Jul 21, 2012, at 6:44 PM, Mike Schinkel <mike at newclarity.net<javascript:;>>
> wrote:
>
> > On Jul 21, 2012, at 8:56 PM, John Blackbourn <johnbillion+wp at gmail.com<javascript:;>>
> 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
> >
> >
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com <javascript:;>
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com <javascript:;>
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>