Posted by rsvelko on August 3, 2009 at 9:50pm
Jump to:
| Project: | Boost |
| Version: | 6.x-1.x-dev |
| Component: | Caching logic |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (works as designed) |
Issue Summary
I am imagining a boost-like html cache not on the page level but working on the subpage level - for each url/page of a site we have html snippets for the different blocks and parts.
So these get cached and thus there is no need for minimum cache lifetime and pre-caching (see http://drupal.org/node/538460 for the efforts on that) but new cached pages are built on node changes and such...
What do you think? Is that even possible?
This sounds like the drupal core caching system but on the last html level - not stopping at the mysql level ...
And maybe if we do this somehow we will lose some performance as compared to the now used page-based caching....
Thoughts?
Comments
#1
This has to do with the way Drupal works. In it's current form Drupal generates data that the theme layer then chooses to use if it wants to. This is what I call a push system; everything gets pushed to the theme layer. Drupal would need to be setup like a pull system where the theme layer makes request and it pulls what it wants. Unless Drupal's internals are seriously reworked, this would be nearly impossible to do correctly. It might work with blocks though, and for that see this discussion: http://groups.drupal.org/node/24825
With your idea, performance wise, your loading up PHP which then defeats the whole purpose of boost. What your proposing is what APC & Memcache sorta do, and they do it quite well.