Closed (outdated)
Project:
Drupal core
Version:
7.x-dev
Component:
base system
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 Apr 2010 at 01:06 UTC
Updated:
20 May 2010 at 10:36 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
mikeytown2 commentedHere is a re-roll of rbuccigrossi's patch for 6.16 and I renamed his function and did some minor code cleanup & documentation. There is also patch from tag1
http://tag1consulting.com/patches/pagecache_lock
Both could potentially use the locking framework and both will suffer from missing js & css files due to aggregation. It would require this patch to land first most likely #721400: Order JS files according to weight, don't change filenames for aggregated JS/CSS & *might* require these functions to be redone
http://api.drupal.org/api/function/drupal_clear_css_cache/6
http://api.drupal.org/api/function/drupal_clear_js_cache/6
Comment #2
FiReaNGeL commentedFrom the blog post :
"In cache_get(), when we are asked to retrieve a page that has a cache entry that expired, we temporarily set the created time to 10 seconds in the future, but return 0 for the current request so that it updates the cache. This allows other requests to get the old cache copy while the current request updates the cache to the latest version. "
Would there be a way to serve the cache for the first request too? Mark as expired, generate it, but serve the cached version so that no user (not even the first one) has to wait?
Also, would it make more sense to port this first to D7 then backport it to D6?
Great feature to have in any way!
Comment #3
catchComment #4
catch