silverstripe-framework/core/manifest
Hamish Friedlander beafcf38db Don't use Zend_Cache in manifests
The overhead of Zend_Cache in manifests is too high - we don't
need LRU or tags, just somewhere to dump a bunch of data that
persists

You can replace the class used by defining SS_MANIFESTCACHE
to be a class that implements the ManifestCache interface
(we can't use the Config system to set this, as it isn't
initialised yet).
2013-03-14 12:07:07 +13:00
..
ClassLoader.php ENHANCEMENT Added $exclusive flag to SS_ClassLoader->pushManifest() to allow for multiple manifests co-existing (useful for tests which rely on core classes but also want to test their own manifests) 2012-04-15 17:17:15 +02:00
ClassManifest.php Don't use Zend_Cache in manifests 2013-03-14 12:07:07 +13:00
ConfigManifest.php FIX Remove instances of lines longer than 120c 2012-09-30 17:18:13 +13:00
ConfigStaticManifest.php Don't use Zend_Cache in manifests 2013-03-14 12:07:07 +13:00
ManifestCache.php Don't use Zend_Cache in manifests 2013-03-14 12:07:07 +13:00
ManifestFileFinder.php MINOR Update @package values to match renaming sapphire 2012-04-15 10:50:19 +12:00
TemplateLoader.php API Explicitly load project template files after modules 2012-12-04 10:47:37 +01:00
TemplateManifest.php Don't use Zend_Cache in manifests 2013-03-14 12:07:07 +13:00
TokenisedRegularExpression.php FIX Remove instances of lines longer than 120c 2012-09-30 17:18:13 +13:00