-
Story
-
Resolution: Done
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
Declarative REST 6, Declarative REST 7, Declarative REST 8, Declarative REST 9
-
8
As a developer, I can configure a caching strategy on a REST connection, so that my integration is performant and cost-effective.
A developer does not want to make too many requests to a remote system, for example if I am hitting a CRM to get information about the current visitor - I dont want to make the REST request everytime the visitor visits a new page.
Also API's can be pay-per-request, or can throttle requests, so making fewer requests can also save money.
Acceptance Criteria:
- Ability to setup a timed cache, and ability to set how often it is cleared.
- Ability to programmatically clear all of the REST connection caches - may or may not handle individual REST caches per client.
- Ability to clear the cache via REST, via a command.
- Caching can be easily configured - probably directly on the REST connection configuration.
- Requests with same URI but different headers do not overlap (e.g. language headers)
Scenarios:
https://wiki.magnolia-cms.com/display/TEASYINT/EasyRest+Cache+Thinking
Acceptance criteria
- is causing
-
MGNLRESTCL-154 DOC: Caching a REST response
- Closed