@@ -14,6 +14,9 @@ The overall aim of this module is twofold:
14142 ) Increase the performance of our applications by reducing the number of, and the complexity of the cache keys that we
1515 calculate at the time of an end user's request.
1616
17+ ** What this module is not** : This module is not here to provide a caching method, it is here to provide you with
18+ ** keys** that you can use with your preferred caching method (EG: partial caching).
19+
1720* [ Installation] ( #installation )
1821* [ Why cache keys are difficult] ( #why-cache-keys-are-difficult )
1922* [ How we aim to solve these difficulties] ( #how-we-aim-to-solve-these-difficulties )
@@ -77,12 +80,12 @@ we have many cache keys that we need to calculate in order to have an accurate c
7780
7881## How we aim to solve these difficulties
7982
80- In short:
83+ ** In short:**
8184We want to move the cost of calculating cache keys to when the changes are made in the CMS, rather than at the time of
8285an end user's request. We will do this by having you configure the links between dependencies, and then we'll manage
8386updating any relevant cache keys when those dependencies change.
8487
85- To reiterate:
88+ ** To reiterate:**
8689We no longer want to create cache keys that contain tonnes or info based on all of our dependencies. Instead, we want to
8790create really simple cache keys which we invalidate when dependencies require them to be.
8891
@@ -297,6 +300,7 @@ See [License](license.md)
297300
298301* Adrian Humphreys <adrhumphreys@gmail.com>
299302* Chris Penny <chris.penny@gmail.com>
303+ * Adrian Jimson <adrian.jimson@silverstripe.com>
300304
301305# # Development and contribution
302306
0 commit comments