A high-performance backend cache system. It is intended for use in speeding up dynamic web applications by alleviating database load. Well implemented, it can drops the database load to almost nothing, yielding faster page load times for users, better resource utilization. It is simple yet powerful.
Added \Phpfastcache\Helper\UninstanciableObjectTrait trait which will contains base locked constructor for any classes that are nor meant to be instanciated.
Deprecated \Phpfastcache\Config\Config::class
Removed/reworked/improved dead/unreachable/redundant/obsolete code, thanks to Phpstan
Drivers
Added Solr driver support
Events
Added \Phpfastcache\Event\EventInterface for \Phpfastcache\Event\Event and subclasses below
Added \Phpfastcache\Drivers\Arangodb\Event for Arangodb events
Added \Phpfastcache\Drivers\Dynamodb\Event for Dynamodb events
Added \Phpfastcache\Drivers\Solr\Event for Solr events
Moved the following constant from \Phpfastcache\Event\Event to their respective drivers: ARANGODB_CONNECTION, ARANGODB_COLLECTION_PARAMS, DYNAMODB_CREATE_TABLE
Cluster
Fixed #855 // ClusterReplication drivers are saving erroneous expiration date in low-level backends
Misc
Full PSR-12 compliance is now enforced by PHPCS
Multiple typo fixes (@mbiebl)
Updated composer suggestions and CI builder dependencies
Types of changes
What types of changes does your code introduce to Phpfastcache?
Put an x in the boxes that apply
[x] Bugfix (non-breaking change which fixes an issue)
[x] Improvement (non-breaking change which improves an existing code/behavior)
[ ] Deprecated third party dependency update
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation/Typo/Resource update that does not involve any code modification
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Proposed changes
9.1.0
04 april 2022
4.1.0(see changes)\Phpfastcache\Helper\UninstanciableObjectTraittrait which will contains base locked constructor for any classes that are nor meant to be instanciated.\Phpfastcache\Config\Config::classPhpstanSolrdriver support\Phpfastcache\Event\EventInterfacefor\Phpfastcache\Event\Eventand subclasses below\Phpfastcache\Drivers\Arangodb\Eventfor Arangodb events\Phpfastcache\Drivers\Dynamodb\Eventfor Dynamodb events\Phpfastcache\Drivers\Solr\Eventfor Solr events\Phpfastcache\Event\Eventto their respective drivers:ARANGODB_CONNECTION,ARANGODB_COLLECTION_PARAMS,DYNAMODB_CREATE_TABLETypes of changes
What types of changes does your code introduce to Phpfastcache? Put an
xin the boxes that applyAgreement
I have read the CONTRIBUTING and CODING GUIDELINE docs
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...