Private update status cache system in Update Status 5.2
We specifically do NOT use the core cache API for saving the fetched data about available updates. It is vitally important that this cache is only cleared when we're populating it after successfully fetching new available update data. Usage of the core cache API results in all sorts of potential problems that would result in attempting to fetch available update data all the time, including if a site has a "minimum cache lifetime" (which is both a minimum and a maximum) defined, or if a site uses memcache or another plug-able cache system that assumes volatile caches.
Update status uses the {cache_update_status} table, but instead of using cache_set(), cache_get(), and cache_clear_all(), there are private helper functions that implement these same basic tasks but ensure that the cache is not prematurely cleared, and that the data is always stored in the database, even if memcache or another cache backend is in use.
File
- ./
update_status.module, line 1823
Functions
Name |
Location | Description |
|---|---|---|
| update_status_invalidate_cache |
./ |
Invalidates all cached data relating to update status. |
| _update_status_cache_clear |
./ |
Invalidates specific cached data relating to update status. |
| _update_status_cache_get |
./ |
Retrieve data from the private update status cache table. |
| _update_status_cache_set |
./ |
Store data in the private update status cache table. |