phpfastcache

When performing operations on tags (e.g., getItemsByTags), you can specify a strategy:

• TAG_STRATEGY_ONE: Get items that match at least ONE of the specified tags. (Default)
• TAG_STRATEGY_ALL: Get items that match ALL of the specified tags.
• TAG_STRATEGY_ONLY: Get items that match ONLY the specified tags (no additional tags allowed).

V7 utilizes PHP 7+ features including strict types (declare(strict_types=1);) and explicit return/scalar type declarations.

When migrating, ensure that the data types you pass to the Phpfastcache API strictly match the expected types defined in the method signatures to avoid type errors.

As of V9.2, there is a distinction between Scoped and Unscoped EventManagers:

1. Scoped EventManager: Retrieved via ExtendedCacheItemPoolTrait::->getEventManager(). It only fires events related to that specific pool instance.
2. Unscoped (Global) EventManager: Accessed via EventManager::getInstance(). It fires events from any pool, regardless of which one emitted them.

Execution Order

When an event is triggered, the execution order is:

1. Scoped named event (getEventManager()->onXxxxx(...))
2. Scoped onEveryEvent event (getEventManager()->onEveryEvent(...))
3. Unscoped named event (EventManager::getInstance()->onXxxxx(...))
4. Unscoped onEveryEvent event (EventManager::getInstance()->onEveryEvents(...))

Phpfastcache provides an event mechanism to intercept and manipulate cache operations at the ItemPool level. You can bind callbacks to specific lifecycle stages of the cache pool.

Warning: Circular Methods Many events have 'Risky Circular Methods'. If you call a method listed under 'Risky Circular Methods' inside your callback, you may trigger an infinite loop (e.g., calling getItem() inside an onCacheGetItem callback).

In V9, certain callback parameters that are not objects are passed by reference using the \Phpfastcache\Event\EventReferenceParameter class.

This class allows you to either read or re-write the original value.

• Reading: The class is invokable; calling it as a function returns the parameter value.
• Writing: Use setParameterValue() to update the value. Note that if the event dispatcher does not allow type changes, attempting to change the type will throw a PhpfastcacheInvalidArgumentException.

This mechanism allows event listeners to modify non-object arguments passed to the event.

The following high-level features were removed in V8:

• ActOnAll helper: Removed in favor of aggregated cluster support.
• fallback feature: Removed. If you need a fallback mechanism when a backend fails to initialize, use an aggregated cluster with a Master/Slave configuration instead.

Phpfastcache provides several development drivers to simulate different caching behaviors during testing:

• Devnull: A driver that returns null for read/hit actions (driverRead(), driverIsHit()) but returns true for write/delete actions (driverDelete(), DriverClear()).
• Devrandom: A driver that returns random data with configurable chance factors and data lengths.

To improve Opcode efficiency, PHPFASTCACHE requires specific prefixing and import patterns for PHP core elements:

• Core Functions: Prefix all core functions with a backslash \.
• Core Constants: Prefix all core constants with a backslash \.
• Core Classes: Do not use use statements to import non-namespaced classes; instead, use the absolute path with a backslash \ during instantiation.

In version 3.0.0, specific byTagsAll() methods were removed and replaced by a more flexible strategy-based approach. Instead of calling dedicated methods for every tag operation, use the standard byTags methods and pass one of the following constants from TaggableCacheItemPoolInterface:

• TAG_STRATEGY_ONE: Matches if at least one tag matches.
• TAG_STRATEGY_ALL: Matches if all tags match.
• TAG_STRATEGY_ONLY: Matches if only the provided tags match.