#16658 closed enhancement (maybelater)
Reverse expiry check for wp_cache functions
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Cache API | Keywords: | reporter-feedback close |
Focuses: | Cc: |
Description
The basic idea is that expiry details are not stored within the cache at all. Expiry is rather a part of the 'get' call. The idea is that cached data is stored with a timestamp instead of expiry. In short, the get function (wp_cache_get) will validate is the cache has expired or not using the timestamp set by the add / set function.
This will give access (if needed) to expired cache too.
Change History (3)
Note: See
TracTickets for help on using
tickets.
What is the problem you are trying to solve?
You have proposed a solution to something not a problem which makes it really hard to triage this ticket.
We need to know what the problem is so that we can ensure we implement the best solution - or point you at how to implement the solution you require in a plugin.