resolving section and fields, namely looking up field configuration in sym_fields and the sym_fields_ tables.selecting a list of all extensions and their delegate subscriptions from the database.However I do think caching could be used internally for repetitive tasks that occur on every page load: The above is just one way, and it would be restrictive for Symphony to force developers to use one method. Data caching is so personal to your application that there are so many ways in which it can and should be implemented. I am not suggesting data source caching goes into the core. This got me thinking about how we might be able to add caching into Symphony's core, and where it would be appropriate. You can see in the example above that the object is cached for one minute ( 60 seconds). You can try this out using MAMP by selecting "APC" from the Cache dropdown (MAMP Pro). Exactly the same principle applies for memcache. This checks that APC is available on your server, and stores the data source XML and param pool (including output parameters) in the cache. If($this->_force_empty_result) $result = $this->emptyXMLSet() $result->appendChild(new XMLElement('error', $e->getMessage())) $result = new XMLElement($this->dsParamROOTELEMENT) cache is still good, return cached XML and param pool If (function_exists('apc_fetch')) $data = apc_fetch($cache_key)
0 kommentar(er)
