Changes between Version 2 and Version 3 of Ticket #59592, comment 5
- Timestamp:
- 10/11/2023 10:55:42 PM (12 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #59592, comment 5
v2 v3 5 5 This all seems to roughly echo what Peter Wilson said in his initial comment: https://core.trac.wordpress.org/ticket/57625#comment:3 6 6 7 Perhaps a solution the present problems is to give users and plugins more control over caching policies such as whether to apply a TTL or not to a specific cache key? Also, to provide documentation/guidance on proper server cache (redis) config - both for users who manage their own servers, as well as for hosting providers to do a better job at.7 The proposed solution here seems to add unnecessary complexity and processing overhead. So, perhaps a solution the present problems is to give users and plugins more control over caching policies such as whether to apply a TTL or not to a specific cache key? Also, to provide documentation/guidance on proper server cache (redis) config - both for users who manage their own servers, as well as for hosting providers to do a better job at. 8 8 9 9 This article from Ruby on Rails goes into detail about using key-based cache expiration, so it seems worth reviewing for inspiration.