[MGNLPN-112] Bypass cache for personalized pages Created: 14/May/14  Updated: 08/Oct/14  Resolved: 16/May/14

Status: Closed
Project: Magnolia Personalization
Component/s: Integration
Affects Version/s: None
Fix Version/s: 1.0

Type: Task Priority: Neutral
Reporter: Philip Mundt Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: cache
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLADVCACHE-29 EagerRecacheCachePolicy doesn't take ... Closed
supersession
is superseded by MGNLPN-189 Remove personalisation-specific cache... Closed
is superseded by MGNLCACHE-57 Avoid unnecessary cache locking for u... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Date of First Response:
Epic Link: Personalisation

 Description   

For the time being we should prevent caching of personalized pages only and keep the cache working for all other pages.



 Comments   
Comment by Magnolia International [ 16/May/14 ]

Done - in branch MGNLPN-112-cache. This works by actually storing an instance of UncacheableEntry in the cache, and a custom CachePolicy which returns bypass when such an entry is found in the cache.

This means that while the first time a page with variant is hit through the cache, concurrent requests are locked. Once the UncacheableEntry is in the cache entry however, concurrent requests won't be locked anymore.

Generated at Mon Feb 12 06:34:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.