Make WordPress Core

Opened 13 years ago

Closed 12 years ago

Last modified 12 years ago

#16658 closed enhancement (maybelater)

Reverse expiry check for wp_cache functions

Reported by: akshay_raje's profile akshay_raje Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Cache API Keywords: reporter-feedback close
Focuses: Cc:


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)

#1 @westi
13 years ago

  • Keywords reporter-feedback added; 2nd-opinion removed

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.

#2 @akshay_raje
12 years ago

  • Keywords close added
  • Resolution set to maybelater
  • Status changed from new to closed

#3 @dd32
12 years ago

  • Milestone Awaiting Review deleted

Just like to mention, that the hardest part of ever implementing this, would be getting all the drop in cache's to support it.. it usually takes 2-3 versions before it's widely supported IMO.

Note: See TracTickets for help on using tickets.