$content : \midcom_services_cache_module_content
This class is the central access point for all registered caching services. Currently this includes the NAP, Memcache, Content and PHPscripts cache databases.
The system is twofold:
There are cache backends, which are responsible for the actual storage and retrieval of cache information, and cache modules, which provide caching services to the application developer.
Check the documentation of the backends for configuring the cache on your live site (as an administrator).
Check the documentation of the cache modules to learn how to take advantage of the cache services available (as a component/core author).
The cache service is independent from the MidCOM Core, as it has to be started up at the beginning of the request. Cache modules are loaded on-demand.
This class will be available throughout he midcom service getter under the handle cache. The content cache module, for backwards compatibility, will be available as $midcom->cache.
All loaded modules will also be available as direct members of this class, you have to ensure the module is loaded in advance though. The class will automatically load all modules which are configured in the autoload_queue in the cache configuration.
invalidate(mixed $guid, string $skip_module = '')
Invalidates all cache records associated with a given content object.
This is either a GUID or a MidgardObject, in which case the Guid is auto-determined.
If specified, the module mentioned here is skipped during invalidation. This option should be avoided by component authors at all costs, it is there for optimizations within the core cache modules (which sometimes need to invalidate only other modules, and invalidate themselves implicitly).