RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2025-02-09 00:39:25 +03:00
Code Issues Projects Releases Wiki Activity

Fix class name: AbstractCache -> CacheProvider

Browse Source
This commit is contained in:
Carsten Blüm 2015-09-19 08:34:00 +02:00
parent 8b79fe9d9b
commit 42a500a73d
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/en/reference/caching.rst
View File

@ -13,7 +13,7 @@ Cache Drivers
The cache drivers follow a simple interface that is defined in The cache drivers follow a simple interface that is defined in
``Doctrine\Common\Cache\Cache``. All the cache drivers extend a ``Doctrine\Common\Cache\Cache``. All the cache drivers extend a
base class ``Doctrine\Common\Cache\AbstractCache`` which implements base class ``Doctrine\Common\Cache\CacheProvider`` which implements
this interface. this interface.
The interface defines the following public methods for you to implement: The interface defines the following public methods for you to implement:
@ -24,7 +24,7 @@ The interface defines the following public methods for you to implement:
- save($id, $data, $lifeTime = false) - Puts data into the cache - save($id, $data, $lifeTime = false) - Puts data into the cache
- delete($id) - Deletes a cache entry - delete($id) - Deletes a cache entry
Each driver extends the ``AbstractCache`` class which defines a few Each driver extends the ``CacheProvider`` class which defines a few
abstract protected methods that each of the drivers must abstract protected methods that each of the drivers must
implement: implement:
@ -38,7 +38,7 @@ The public methods ``fetch()``, ``contains()`` etc. use the
above protected methods which are implemented by the drivers. The above protected methods which are implemented by the drivers. The
code is organized this way so that the protected methods in the code is organized this way so that the protected methods in the
drivers do the raw interaction with the cache implementation and drivers do the raw interaction with the cache implementation and
the ``AbstractCache`` can build custom functionality on top of the ``CacheProvider`` can build custom functionality on top of
these methods. these methods.
This documentation does not cover every single cache driver included This documentation does not cover every single cache driver included