[wp-hackers] Caching as part of the core
Brian Layman
wp-hackers at thecodecave.com
Sun Jul 22 17:31:58 UTC 2012
Actually it's not a bad thing. Drop in plugins are what they are because
they must be loaded early on, or at least at very specific times in the
initiation process, to do their job.
They are so specific in function, that the list of file names is hard
coded into the core.
Here's a currentish list:
|If you look for the function _get_dropins() in
wp-admin/includes/plugin.php|, you'll see there is a lit of the current
dropdin functions.
$dropins = array(
'advanced-cache.php' => array( __( 'Advanced caching
plugin.' ), 'WP_CACHE' ), // WP_CACHE
'db.php' => array( __( 'Custom database
class.' ), true ), // auto on load
'db-error.php' => array( __( 'Custom database error
message.' ), true ), // auto on error
'install.php' => array( __( 'Custom install
script.' ), true ), // auto on install
'maintenance.php' => array( __( 'Custom maintenance
message.' ), true ), // auto on maintenance
'object-cache.php' => array( __( 'External object
cache.' ), true ), // auto on load
);
if ( is_multisite() ) {
$dropins['sunrise.php' ] = array( __( 'Executed before
Multisite is loaded.' ), 'SUNRISE' ); // SUNRISE
$dropins['blog-deleted.php' ] = array( __( 'Custom site
deleted message.' ), true ); // auto on deleted blog
$dropins['blog-inactive.php' ] = array( __( 'Custom site
inactive message.' ), true ); // auto on inactive blog
$dropins['blog-suspended.php'] = array( __( 'Custom site
suspended message.' ), true ); // auto on archived or spammed blog
}
return $dropins;
Brian Layman
On 7/22/2012 11:52 AM, Almog Baku wrote:
> That idea, of drop-ins is really bad. Because it hack the core.
> I belive that any unoffical hacking(not aproved patch) is bad because well
> known obviuse reasons.
>
> Are you sure that the current plugins using it?
> If they are it just proof my point.
>
> בתאריך יום ראשון, 22 ביולי 2012, Mike Schinkel כתב:
>
>> On Jul 22, 2012, at 3:31 AM, Chason Chaffin wrote:
>>> While I agree that fragment caching would be useful, it sounds like
>> something that would be better as a plugin,
>>
>> Core uses a drop-in[1] for handling caching which means only one caching
>> plugin unless plugins are explicitly designed to work together. As there
>> are many different ways to do caching you can get any flavor available, but
>> you can only that one flavor.
>>
>> To enable innovation in caching for WordPress the drop-in concept in core
>> needs to be changed to enable multiple plugins to handle different aspects
>> of caching. Currently advanced caching (pun intended) is really only viable
>> for programmers with the time to invest.
>>
>>> since generalizing it would be a difficult problem,
>> Why do you assume that?
>>
>> -Mike
>> [1] http://hakre.wordpress.com/2010/05/01/must-use-and-drop-ins-plugins/
>> _______________________________________________
>> 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
> http://lists.automattic.com/mailman/listinfo/wp-hackers
More information about the wp-hackers
mailing list