[wp-hackers] Caching as part of the core

[Almog Baku]

On Tue, Jul 24, 2012 at 7:21 PM, Otto <otto at ottodestruct.com> wrote:

> > And about the caching interface in the current basic/common hooks.. what?
>
> I don't understand the question you're asking here.


I asked what about the adding the cache to the API as option to the basic
hooks as I suggest before:
> The base caching/optimization will include:
>
> minification: html, js, css:
>
> interface:
> wp_enqueue_script( $handle, $src = false, $deps = array(), $ver = false,
> $in_footer = false, $minify=AUTO_MINIFY )
> wp_register_style( $handle, $src, $deps = array(), $ver = false, $media =
> 'all', $minify=AUTO_MINIFY )
>
> combination: combine js, css files:
>
> interface:
> wp_enqueue_script( $handle, $src = false, $deps = array(), $ver = false,
> $in_footer = false, $minify=AUTO_MINIFY, $combine=AUTO_COMBINE )
> wp_register_style( $handle, $src, $deps = array(), $ver = false, $media =
> 'all', $minify=MINIFY_DISABLED, $combine=AUTO_COMBINE )
>
> basic object caching- at least as api interface without implemention!:
> extending the object caching api: adding option to control the object
> caching within the development- like widgets, pages, etc
>
> interface:
> register_sidebar(array(
>     'name'     => __( 'Post Sidebar'),
>     'id'     => 'post-sidebar',
>     ...
>     'cache'    => AUTO_CACHE,
> ));
> register_nav_menus(array(
>     'top_nav' => __( 'Top Navigation'),
>     ...
>     'cache'    => AUTO_CACHE,
> ));
> register_post_type('slider', array(
>     'label' => __('Slider'),
>     ...
>     'cache'=> AUTO_CACHE,
> ));