Changes between Version 1 and Version 2 of Ticket #57789, comment 2
- Timestamp:
- 02/22/2023 10:33:09 PM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #57789, comment 2
v1 v2 3 3 Each logged-in non-ajax admin requests could, at least once, always fetch the theme.json. If there are changes from what is in the persistent cache then it can update. As a backup (in case a theme is updated but nobody logs in), could also allow the same invalidation-checks during cron as well. 4 4 5 Worst case scenario: no cron is running and no admin-side log-ins are occurring. In which case it'd just have to rely on the TTL expiring and a frontend would have to do the work to populate the cache again.5 Worst case scenario: no cron is running and no admin-side log-ins are occurring. In which case it'd just have to rely on the TTL expiring and a frontend request would have to do the work to populate the cache again. 6 6 7 7 This gives the benefits of persistent cache, while solving for invalidation in a pretty reasonable way.