Download the PHP package gwa/gw-cache without Composer
On this page you can find all versions of the php package gwa/gw-cache. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package gw-cache
Short Description PHP simple cache classes
License MIT
Homepage https://github.com/gwa/gwCache
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package gw-cache
gwCache
A simple but flexible PHP cache
Usage
Installation
Install package via composer.
Using the cache
Using a factory
Instead of always passing in the persistence layer, a factory can be used.
The factory could be set up as a service in your app (using, for example, Pimple). Creating a cache instance is then not dependent on the persistence layer.
Caching serialized data
To cache complex PHP types (ie. objects), set the cache type argument when creating the cache instance.
Custom persistence layers
You can roll your own persistence layer (MySQL, memcache, redis) by creating a class that implements the CachePersistenceInterface interface.
If you are using a factory-as-a-service architecture, you can use different persistence layers in different environments without changing the code that uses the service.
Contributing
All code contributions - including those of people having commit access - must go through a pull request and approved by a core developer before being merged. This is to ensure proper review of all the code.
Fork the project, create a feature branch, and send us a pull request.
To ensure a consistent code base, you should make sure the code follows the Coding Standards which we borrowed from PSR-2.
The easiest way to do make sure you're following the coding standard is to run vendor/bin/php-cs-fixer fix before committing.
