Quote from: sirlancelot at Jun 08, 2007, 04:31 PM
It seems the roadmap contains two instances of "Database result-set caching", one being more detailed than the other, any reason for this?
The first one is about halfway down the page, and the second one is the last bullet point under the "Even more extensible; even less hacking" bullet point at the end of the document.
Right, the first describes the default implementation provided with the MODx core, and the second refers to how you can override or extend that implementation by providing your own class that extends the core classes. You simply configure the providers for each service via the site configuration (which can also be overridden by context or programmatically via API). For instance, to provide a custom db result-set caching service, you would simply define the config setting
cache_db_handler, either programmatically, via context settings, or via core system settings. e.g.
<?php
require_once(MODX_CORE_PATH . 'mylibrary/classes/myCustomCacheClass.class.php');
$modx->config['cache_db_handler']= 'myCustomCacheClass';
?>
By implementing the same methods implemented in the xPDOFileCache class (which is the default db result-set provider), you can easily cache it using whatever method you choose...
Quote from: sirlancelot at Jun 08, 2007, 04:31 PM
Also Jason, you may want to update the link to the roadmap in your first post, it’s returning a 404 
Updated, thanks for the reminder...
MODX Staff
