hook_init() necessity [#1063316]

I'm looking into enabling aggressive caching mode on a site of mine. One of the modules that may stop working properly, is the css_gzip module. Now, from what I've read in the issue queue and in the code, it seems the hook_init() and hook_exit() implementations are only necessary for recolored themes?

If so, could you please confirm this and document it in the README? Thank you! :)

Comments

Comment #1

mikeytown2 CreditAttribution: mikeytown2 commented 16 February 2011 at 18:27

First request will gzip the css file. Documentation is important; need to do this...

Sidenote:
#1063012: replacement I've come up with a replacement for css/js aggregation; one that has a smart file naming convention and doesn't cause 404's if using an external page cache. bundle cache seems abandoned. And the Advanced Aggregation module is similar to it. Whats your take on this? We seem to have similar goals (Parallel vs CDN) so working together whenever possible seems like a good idea. Looking over your bundle cache code, it seems to have a lot of database tables; is that necessary? I'm going to build AA as a all in one package, with several sub modules like css compression, unlimited IE css, jsmin & google cdn for jQuery. It's kinda a dick move but css/js optimizations in D6 is badly broken. I plan on giving CVS to any maintainer that I rip code from as this seems like the best way to accomplish this without being a total jerk. One thing boost has taught me is that people like a download that does what they need. It also taught me that too many configuration options is a bad idea.