backdrop-contrib / memcache

High performance integration with memcache.
2 stars 1 forks source link

Issue #1: Avoid state system and database dependence. #2

Closed quicksketch closed 1 year ago

quicksketch commented 1 year ago

Fixes #1 by using memcache itself to store the flush/garbage collection/wildcard clear timestamps. To prevent any of this critical data from being cleaned up by memcache's LRU (least recently used) algorithm, I consolidated all the bin-specific settings into an array and stored it in the "bootstrap" bin. This should make it so that the flush/gc state for all bins is retrieved every request, so it is unlikely they will be removed.

This also cleans up the terminology to line up with the newer cache system in Backdrop core, preferring "garbage collection" to "temporary flush".