Search moodle.org's
Developer Documentation

See Release Notes

  • Bug fixes for general core bugs in 3.11.x will end 14 Nov 2022 (12 months plus 6 months extension).
  • Bug fixes for security issues in 3.11.x will end 13 Nov 2023 (18 months plus 12 months extension).
  • PHP version: minimum PHP 7.3.0 Note: minimum PHP version has increased since Moodle 3.10. PHP 7.4.x is supported too.
/cache/classes/ -> interfaces.php (source)

[Source view]

Differences Between: [Versions 311 and 400] [Versions 311 and 401] [Versions 311 and 402] [Versions 311 and 403]

Cache API interfaces This file is part of Moodle's cache API, affectionately called MUC. It contains the components that are requried in order to use caching.

Copyright: 2012 Sam Hemelryk
License: http://www.gnu.org/copyleft/gpl.html GNU GPL v3 or later
File Size: 524 lines (22 kb)
Included or required:0 times
Referenced: 0 times
Includes or requires: 0 files

Defines 9 classes

cache_loader:: (9 methods):
  get()
  get_many()
  set()
  set_many()
  has()
  has_any()
  has_all()
  delete()
  delete_many()

cache_loader_with_locking:: (3 methods):
  acquire_lock()
  check_lock_state()
  release_lock()

cache_is_lockable:: (3 methods):
  acquire_lock()
  check_lock_state()
  release_lock()

cache_is_key_aware:: (3 methods):
  has()
  has_any()
  has_all()

cache_is_searchable:: (2 methods):
  find_all()
  find_by_prefix()

cache_is_configurable:: (2 methods):
  config_get_configuration_array()
  config_set_edit_form_data()

cache_data_source:: (3 methods):
  get_instance_for_cache()
  load_for_cache()
  load_many_for_cache()

cacheable_object:: (2 methods):
  prepare_to_cache()
  wake_from_cache()

cache_lock_interface:: (5 methods):
  __construct()
  lock()
  unlock()
  check_state()
  __destruct()


Interface: cache_loader  - X-Ref

Cache Loader.

This cache loader interface provides the required structure for classes that wish to be interacted with as a
means of accessing and interacting with a cache.

Can be implemented by any class wishing to be a cache loader.
get($key, $strictness = IGNORE_MISSING)   X-Ref
Retrieves the value for the given key from the cache.

param: string|int $key The key for the data being requested.
param: int $strictness One of IGNORE_MISSING or MUST_EXIST.
return: mixed The data retrieved from the cache, or false if the key did not exist within the cache.

get_many(array $keys, $strictness = IGNORE_MISSING)   X-Ref
Retrieves an array of values for an array of keys.

Using this function comes with potential performance implications.
Not all cache stores will support get_many/set_many operations and in order to replicate this functionality will call
the equivalent singular method for each item provided.
This should not deter you from using this function as there is a performance benefit in situations where the cache
store does support it, but you should be aware of this fact.

param: array $keys The keys of the data being requested.
param: int $strictness One of IGNORE_MISSING or MUST_EXIST.
return: array An array of key value pairs for the items that could be retrieved from the cache.

set($key, $data)   X-Ref
Sends a key => value pair to the cache.

<code>
// This code will add four entries to the cache, one for each url.
$cache->set('main', 'http://moodle.org');
$cache->set('docs', 'http://docs.moodle.org');
$cache->set('tracker', 'http://tracker.moodle.org');
$cache->set('qa', 'http://qa.moodle.net');
</code>

param: string|int $key The key for the data being requested.
param: mixed $data The data to set against the key.
return: bool True on success, false otherwise.

set_many(array $keyvaluearray)   X-Ref
Sends several key => value pairs to the cache.

Using this function comes with potential performance implications.
Not all cache stores will support get_many/set_many operations and in order to replicate this functionality will call
the equivalent singular method for each item provided.
This should not deter you from using this function as there is a performance benefit in situations where the cache store
does support it, but you should be aware of this fact.

<code>
// This code will add four entries to the cache, one for each url.
$cache->set_many(array(
'main' => 'http://moodle.org',
'docs' => 'http://docs.moodle.org',
'tracker' => 'http://tracker.moodle.org',
'qa' => ''http://qa.moodle.net'
));
</code>

param: array $keyvaluearray An array of key => value pairs to send to the cache.
return: int The number of items successfully set. It is up to the developer to check this matches the number of items.

has($key)   X-Ref
Test is a cache has a key.

The use of the has methods is strongly discouraged. In a high load environment the cache may well change between the
test and any subsequent action (get, set, delete etc).
Instead it is recommended to write your code in such a way they it performs the following steps:
<ol>
<li>Attempt to retrieve the information.</li>
<li>Generate the information.</li>
<li>Attempt to set the information</li>
</ol>

Its also worth mentioning that not all stores support key tests.
For stores that don't support key tests this functionality is mimicked by using the equivalent get method.
Just one more reason you should not use these methods unless you have a very good reason to do so.

param: string|int $key
return: bool True if the cache has the requested key, false otherwise.

has_any(array $keys)   X-Ref
Test if a cache has at least one of the given keys.

It is strongly recommended to avoid the use of this function if not absolutely required.
In a high load environment the cache may well change between the test and any subsequent action (get, set, delete etc).

Its also worth mentioning that not all stores support key tests.
For stores that don't support key tests this functionality is mimicked by using the equivalent get method.
Just one more reason you should not use these methods unless you have a very good reason to do so.

param: array $keys
return: bool True if the cache has at least one of the given keys

has_all(array $keys)   X-Ref
Test is a cache has all of the given keys.

It is strongly recommended to avoid the use of this function if not absolutely required.
In a high load environment the cache may well change between the test and any subsequent action (get, set, delete etc).

Its also worth mentioning that not all stores support key tests.
For stores that don't support key tests this functionality is mimicked by using the equivalent get method.
Just one more reason you should not use these methods unless you have a very good reason to do so.

param: array $keys
return: bool True if the cache has all of the given keys, false otherwise.

delete($key, $recurse = true)   X-Ref
Delete the given key from the cache.

param: string|int $key The key to delete.
param: bool $recurse When set to true the key will also be deleted from all stacked cache loaders and their stores.
return: bool True of success, false otherwise.

delete_many(array $keys, $recurse = true)   X-Ref
Delete all of the given keys from the cache.

param: array $keys The key to delete.
param: bool $recurse When set to true the key will also be deleted from all stacked cache loaders and their stores.
return: int The number of items successfully deleted.

Interface: cache_loader_with_locking  - X-Ref

Cache Loader supporting locking.

This interface should be given to classes already implementing cache_loader that also wish to support locking.
It outlines the required structure for utilising locking functionality when using a cache.

Can be implemented by any class already implementing the cache_loader interface.
acquire_lock($key)   X-Ref
Acquires a lock for the given key.

Please note that this happens automatically if the cache definition requires locking.
it is still made a public method so that adhoc caches can use it if they choose.
However this doesn't guarantee consistent access. It will become the responsibility of the calling code to ensure
locks are acquired, checked, and released.

param: string|int $key
return: bool True if the lock could be acquired, false otherwise.

check_lock_state($key)   X-Ref
Checks if the cache loader owns the lock for the given key.

Please note that this happens automatically if the cache definition requires locking.
it is still made a public method so that adhoc caches can use it if they choose.
However this doesn't guarantee consistent access. It will become the responsibility of the calling code to ensure
locks are acquired, checked, and released.

param: string|int $key
return: bool True if this code has the lock, false if there is a lock but this code doesn't have it,

release_lock($key)   X-Ref
Releases the lock for the given key.

Please note that this happens automatically if the cache definition requires locking.
it is still made a public method so that adhoc caches can use it if they choose.
However this doesn't guarantee consistent access. It will become the responsibility of the calling code to ensure
locks are acquired, checked, and released.

param: string|int $key
return: bool True if the lock has been released, false if there was a problem releasing the lock.

Interface: cache_is_lockable  - X-Ref

Cache store feature: locking

This is a feature that cache stores can implement if they wish to support locking themselves rather
than having the cache loader handle it for them.

Can be implemented by classes already implementing cache_store.
acquire_lock($key, $ownerid)   X-Ref
Acquires a lock on the given key for the given identifier.

param: string $key The key we are locking.
param: string $ownerid The identifier so we can check if we have the lock or if it is someone else.
return: bool True if the lock could be acquired, false otherwise.

check_lock_state($key, $ownerid)   X-Ref
Test if there is already a lock for the given key and if there is whether it belongs to the calling code.

param: string $key The key we are locking.
param: string $ownerid The identifier so we can check if we have the lock or if it is someone else.
return: bool True if this code has the lock, false if there is a lock but this code doesn't have it, null if there

release_lock($key, $ownerid)   X-Ref
Releases the lock on the given key.

param: string $key The key we are locking.
param: string $ownerid The identifier so we can check if we have the lock or if it is someone else.
return: bool True if the lock has been released, false if there was a problem releasing the lock.

Interface: cache_is_key_aware  - X-Ref

Cache store feature: key awareness.

This is a feature that cache stores and cache loaders can both choose to implement.
If a cache store implements this then it will be made responsible for tests for items within the cache.
If the cache store being used doesn't implement this then it will be the responsibility of the cache loader to use the
equivalent get methods to mimick the functionality of these tests.

Cache stores should only override these methods if they natively support such features or if they have a better performing
means of performing these tests than the handling that would otherwise take place in the cache_loader.

Can be implemented by classes already implementing cache_store.
has($key)   X-Ref
Test is a cache has a key.

The use of the has methods is strongly discouraged. In a high load environment the cache may well change between the
test and any subsequent action (get, set, delete etc).
Instead it is recommended to write your code in such a way they it performs the following steps:
<ol>
<li>Attempt to retrieve the information.</li>
<li>Generate the information.</li>
<li>Attempt to set the information</li>
</ol>

Its also worth mentioning that not all stores support key tests.
For stores that don't support key tests this functionality is mimicked by using the equivalent get method.
Just one more reason you should not use these methods unless you have a very good reason to do so.

param: string|int $key
return: bool True if the cache has the requested key, false otherwise.

has_any(array $keys)   X-Ref
Test if a cache has at least one of the given keys.

It is strongly recommended to avoid the use of this function if not absolutely required.
In a high load environment the cache may well change between the test and any subsequent action (get, set, delete etc).

Its also worth mentioning that not all stores support key tests.
For stores that don't support key tests this functionality is mimicked by using the equivalent get method.
Just one more reason you should not use these methods unless you have a very good reason to do so.

param: array $keys
return: bool True if the cache has at least one of the given keys

has_all(array $keys)   X-Ref
Test is a cache has all of the given keys.

It is strongly recommended to avoid the use of this function if not absolutely required.
In a high load environment the cache may well change between the test and any subsequent action (get, set, delete etc).

Its also worth mentioning that not all stores support key tests.
For stores that don't support key tests this functionality is mimicked by using the equivalent get method.
Just one more reason you should not use these methods unless you have a very good reason to do so.

param: array $keys
return: bool True if the cache has all of the given keys, false otherwise.

Interface: cache_is_searchable  - X-Ref

Cache store feature: keys are searchable.

Cache stores can choose to implement this interface.
In order for a store to be usable as a session cache it must implement this interface.

find_all()   X-Ref
Finds all of the keys being used by the cache store.

return: array.

find_by_prefix($prefix)   X-Ref
Finds all of the keys whose keys start with the given prefix.

param: string $prefix

Interface: cache_is_configurable  - X-Ref

Cache store feature: configurable.

This feature should be implemented by all cache stores that are configurable when adding an instance.
It requires the implementation of methods required to convert form data into the a configuration array for the
store instance, and then the reverse converting configuration data into an array that can be used to set the
data for the edit form.

Can be implemented by classes already implementing cache_store.
config_get_configuration_array($data)   X-Ref
Given the data from the add instance form this function creates a configuration array.

param: stdClass $data
return: array

config_set_edit_form_data(moodleform $editform, array $config)   X-Ref
Allows the cache store to set its data against the edit form before it is shown to the user.

param: moodleform $editform
param: array $config

Interface: cache_data_source  - X-Ref

Cache Data Source.

The cache data source interface can be implemented by any class within Moodle.
If implemented then the class can be reference in a cache definition and will be used to load information that cannot be
retrieved from the cache. As part of its retrieval that information will also be loaded into the cache.

This allows developers to created a complete cache solution that can be used through code ensuring consistent cache
interaction and loading. Allowing them in turn to centralise code and help keeps things more easily maintainable.

Can be implemented by any class.

get_instance_for_cache(cache_definition $definition)   X-Ref
Returns an instance of the data source class that the cache can use for loading data using the other methods
specified by this interface.

param: cache_definition $definition
return: object

load_for_cache($key)   X-Ref
Loads the data for the key provided ready formatted for caching.

param: string|int $key The key to load.
return: mixed What ever data should be returned, or false if it can't be loaded.

load_many_for_cache(array $keys)   X-Ref
Loads several keys for the cache.

param: array $keys An array of keys each of which will be string|int.
return: array An array of matching data items.

Interface: cacheable_object  - X-Ref

Cacheable object.

This interface can be implemented by any class that is going to be passed into a cache and allows it to take control of the
structure and the information about to be cached, as well as how to deal with it when it is retrieved from a cache.
Think of it like serialisation and the __sleep and __wakeup methods.
This is used because cache stores are responsible for how they interact with data and what they do when storing it. This
interface ensures there is always a guaranteed action.
prepare_to_cache()   X-Ref
Prepares the object for caching. Works like the __sleep method.

return: mixed The data to cache, can be anything except a class that implements the cacheable_object... that would

wake_from_cache($data)   X-Ref
Takes the data provided by prepare_to_cache and reinitialises an instance of the associated from it.

param: mixed $data
return: object The instance for the given data.

Interface: cache_lock_interface  - X-Ref

Cache lock interface

This interface needs to be inherited by all cache lock plugins.
__construct($name, array $configuration = array()   X-Ref
Constructs an instance of the cache lock given its name and its configuration data

param: string $name The unique name of the lock instance
param: array $configuration

lock($key, $ownerid, $block = false)   X-Ref
Acquires a lock on a given key.

param: string $key The key to acquire a lock for.
param: string $ownerid An unique identifier for the owner of this lock. It is entirely optional for the cache lock plugin
param: bool $block If set to true the application will wait until a lock can be acquired
return: bool True if the lock can be acquired false otherwise.

unlock($key, $ownerid, $forceunlock = false)   X-Ref
Releases the lock held on a certain key.

param: string $key The key to release the lock for.
param: string $ownerid An unique identifier for the owner of this lock. It is entirely optional for the cache lock plugin
param: bool $forceunlock If set to true the lock will be removed if it exists regardless of whether or not we own it.

check_state($key, $ownerid)   X-Ref
Checks the state of the given key.

Returns true if the key is locked and belongs to the ownerid.
Returns false if the key is locked but does not belong to the ownerid.
Returns null if there is no lock

param: string $key The key we are checking for.
param: string $ownerid The identifier so we can check if we have the lock or if it is someone else.
return: bool True if this code has the lock, false if there is a lock but this code doesn't have it, null if there

__destruct()   X-Ref
Cleans up any left over locks.

This function MUST clean up any locks that have been acquired and not released during processing.
Although the situation of acquiring a lock and not releasing it should be insanely rare we need to deal with it.
Things such as unfortunate timeouts etc could cause this situation.