Details
-
Improvement
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
2.0.0
-
None
Description
It would be great to have a caching option be available for a single request. This is especially helpful when we have components that need to get access from a third party API that is personalized and cannot be cached. However, we do want to avoid the component from doing the request X time for the number of times the component is on the page.
For example: a page contains a BloomReach Facets Component and a product grid. In there we need access to the results of the Personalization API. Both components use the same result, but after the user clicks on a link, the 1 on 1 personalization API can return new results in the next request. In other words: we should hold the result for only the request and not longer.
Attachments
Issue Links
- causes
-
CRISP-18 NPE when using CRISP broker service when invoked from custom CMS plugin module
- Closed