L-electron-Rare/moodle
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

MDL-36111 cache: Fixed up typo's and trivial issues

Browse Source
This commit is contained in:
Sam Hemelryk
2012-11-12 10:36:53 +13:00
parent 8ccaa296fa
commit 758dbdf894
11 changed files with 30 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cache/classes/interfaces.php
Vendored
+7 -7
View File
@@ -194,8 +194,8 @@ interface cache_loader_with_locking {
*
* 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 reponsiblity of the calling code to ensure locks
* are acquired, checked, and released.
* 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.
@@ -207,8 +207,8 @@ interface cache_loader_with_locking {
*
* 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 reponsiblity of the calling code to ensure locks
* are acquired, checked, and released.
* 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,
@@ -221,8 +221,8 @@ interface cache_loader_with_locking {
*
* 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 reponsiblity of the calling code to ensure locks
* are acquired, checked, and released.
* 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.
@@ -314,7 +314,7 @@ interface cache_store {
*
* @return bool
*/
public function supports_multiple_indentifiers();
public function supports_multiple_identifiers();
/**
* Returns true if this cache store instance promotes data guarantee.