Table of Contents
- Why use Symfony/Cache and Symfony/Config component?
- Why not using Guzzle?
- Why not using Swagger Codegen?
- Which PHP compatibility matrix?
We explain here each important technical decision used to design this library.
The Cache component is compatible with many cache systems.
The Config component provides several classes to help you find, load, combine, fill and validate configuration values of any kind, whatever their source may be (YAML, XML, INI files, or for instance a database). A great job done by this library, tested and maintained under LTS versions.
This library is tested and maintained under LTS versions.
The last Guzzle versions remove the User-Agent to prevent risks. Since LAPI or CAPI need a valid User-Agent, we can not use Guzzle to request CAPI/LAPI.
We were not able to use this client with ease ex: impossible to get JSON data, it seems there is a bug with unserialization, we received an empty array.
Because this PHP version is no more supported since December 2018 (not even a security fix). Also, a lot of libraries are no more compatible with this version. We don't want to use an older version of these libraries because Composer can only install one version of each extension/package. So, being compatible with this old PHP version means to be not compatible with projects using a new version of these libraries.
These PHP versions are not anymore maintained for security fixes since 2019. We encourage you a lot to upgrade your PHP version. You can view the full list of PHP versions lifecycle.
To get a robust library and not provide security bug unmaintained, we use components under LTS versioning.
The oldest PHP version compatible with these libraries is PHP 7.2.x.
In order to use Memcached with a PHP 8.x set up, you must have an installed version of the memcached php extension > 3.1.5. To check what is your current version, you could run :
php -r "echo phpversion('memcached');"