MemoryCounterBackend
class MemoryCounterBackend extends MemoryBackend (View source)
Defines a memory cache implementation that counts set and get calls.
This can be used to mock a cache backend where one needs to know how many times a cache entry was set or requested.
Properties
| protected | $cache | Array to store cache objects. |
from MemoryBackend |
| protected array | $counter | Stores a list of cache cid calls keyed by function name. |
Methods
Returns data from the persistent cache.
Returns data from the persistent cache when given an array of cache IDs.
Stores data in the persistent cache.
Deletes an item from the cache.
Marks cache items with any of the specified tags as invalid.
Increase the counter for a function with a certain cid.
Returns the call counter for the get, set and delete methods.
Resets the call counter.
Details
object|false
get(string $cid, bool $allow_invalid = FALSE)
Returns data from the persistent cache.
array
getMultiple(array $cids, bool $allow_invalid = FALSE)
Returns data from the persistent cache when given an array of cache IDs.
protected mixed
prepareItem(object $cache, bool $allow_invalid)
Prepares a cached item.
Checks that items are either permanent or did not expire, and returns data as appropriate.
set(string $cid, mixed $data, int $expire = Cache::PERMANENT, array $tags = [])
Stores data in the persistent cache.
Core cache implementations set the created time on cache item with microtime(TRUE) rather than REQUEST_TIME_FLOAT, because the created time of cache items should match when they are created, not when the request started. Apart from being more accurate, this increases the chance an item will legitimately be considered valid.
setMultiple(array $items = [])
Store multiple items in the persistent cache.
delete(string $cid)
Deletes an item from the cache.
If the cache item is being deleted because it is no longer "fresh", you may consider using invalidate() instead. This allows callers to retrieve the invalid item by calling get() with $allow_invalid set to TRUE. In some cases an invalid item may be acceptable rather than having to rebuild the cache.
deleteMultiple(array $cids)
Deletes multiple items from the cache.
If the cache items are being deleted because they are no longer "fresh", you may consider using invalidateMultiple() instead. This allows callers to retrieve the invalid items by calling get() with $allow_invalid set to TRUE. In some cases an invalid item may be acceptable rather than having to rebuild the cache.
deleteAll()
Deletes all cache items in a bin.
invalidate(string $cid)
Marks a cache item as invalid.
Invalid items may be returned in later calls to get(), if the $allow_invalid argument is TRUE.
invalidateMultiple(array $cids)
Marks cache items as invalid.
Invalid items may be returned in later calls to get(), if the $allow_invalid argument is TRUE.
invalidateTags(array $tags)
Marks cache items with any of the specified tags as invalid.
invalidateAll()
Marks all cache items as invalid.
Invalid items may be returned in later calls to get(), if the $allow_invalid argument is TRUE.
garbageCollection()
Performs garbage collection on a cache bin.
The backend may choose to delete expired or invalidated items.
removeBin()
Remove a cache bin.
protected int
getRequestTime()
Wrapper method for REQUEST_TIME constant.
__sleep()
Prevents data stored in memory backends from being serialized.
reset()
Reset statically cached variables.
This is only used by tests.
protected
increaseCounter(string $function, string $cid)
Increase the counter for a function with a certain cid.
int|array
getCounter(string $method = NULL, string $cid = NULL)
Returns the call counter for the get, set and delete methods.
resetCounter()
Resets the call counter.