Changes between Version 1 and Version 2 of Ticket #35096, comment 8
- Timestamp:
- 12/17/2015 09:10:24 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #35096, comment 8
v1 v2 1 When caching failures cause hundreds of unnecessary queries, and when WordPress is una ware of cache set failures and takes itself offline when they happen, the caching model is fundamentally broken and needs to be fixed. Something as simple as a DNS problem becomes a single point of failure. It's 2016 - how about a success callback?1 When caching failures cause hundreds of unnecessary queries, and when WordPress is unable to make itself aware of cache failures in order to fix itself, the caching model is fundamentally broken and needs to be fixed. Something as simple as a DNS problem becomes a single point of failure. It's 2016 - how about a success callback?