Download the PHP package chh/cache-service-provider without Composer
On this page you can find all versions of the php package chh/cache-service-provider. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 cache-service-provider
Silex Cache Service Provider
This service provider for Silex uses the Doctrine Cache library to provide a cache service to a Silex application as well as
to other service providers.
Install
Install with composer:
% composer require chh/cache-service-providerUsage
Configuration
For an application wide cache use the default cache by setting the default key in cache.options with the cache definition.
The cache definition is an array of options, with driver being the
only mandatory one. All other options in the array, are treated as
constructor arguments to the driver class.
The cache named default is the cache available through the container's
cache service.
The driver name can be one of the following:
- A fully qualified class name of a class which implements the
Doctrine\Common\Cache\Cacheinterface - An alias like "apc", which then gets translated to
\Doctrine\Common\Cache\ApcCache. - A Closure, which returns an object implementing
\Doctrine\Common\Cache\Cache.
This cache is then available through the cache service, and provides
an instance of Doctrine\Common\Cache\Cache:
To configure multiple caches, define them as additional keys in
cache.options:
All caches (including the default) are then available as a key of the caches service:
Usage from within extensions
Extensions should make no assumptions about their environment. Therefore
it's best to use the application's default cache most of the time. But
when you do need a cache with a specific driver, then you can use the
cache.factory service.
This factory takes an array of cache options,
just like in each key of cache.options, and returns a Factory suitable
for Pimple.
Extensions should prefix their cache keys to avoid conflicts with user specified cache IDs.
To make this easier the Cache Service Provider ships with a CacheNamespace class. This
class decorates any \Doctrine\Common\Cache\Cache, and prefixes the
keys on all cache operations.
For caches with builtin namespacing support via a setNamespace method,
there's also a namespace configuration option.
This library also provides the cache.namespace factory, which returns a Closure suitable for assigning directly
to a Pimple container. Using this, the above code can be further simplified:
License
Copyright (c) 2016 Christoph Hochstrasser
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE\
