Posted by brakkar on September 27, 2006 at 12:05am
Jump to:
| Project: | Block Cache |
| Version: | 4.7.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi,
again a great block by Jeff.
Will this module have an upgrade path to 5.0 once it is released ? I understand major modification in cache are going to make it in 5.0 already....
Cordially,
Brakkar
Comments
#1
Yes. It should only take a little bit of modification to get this module to work with 5.0.
-j
#2
IMHO, this module should get included into 5.0 core. Block caching is a great feature that will benefit so many people, in particular all the people complaining about less cache for logged in users.
Brakkar
#3
Well I know that Killes did some work on core-level block caching here:
http://drupal.org/node/80951
You can show your support for it and try to move it along. But the 5.0 code freeze will probably preclude this functionality from getting in before 5.1.
IMO, core-wise, the problem with this module as it stands is that it doubles the number of blocks in the listing. It also has more settings than most novice users might understand. I think the trick is to go in the direction that Killes has gone and allow modules to define their own caching parameters and then reduce the user interface down to something much more simple.
In the meantime, I'll update this module for 5.0 and it should offer the same performance benefits without needing to be part of core.
#4
Thanks for pointing this thread. Indeed, an interesting apporach for core integration.
I guess cache blocks feature will make it into core into a form or another in 5.1 or later.
Brakkar
#5