On Wed, 28 Oct 2009 15:59:45 Cliff Black wrote: > Mod_cache caches final html output - essentially making it a static page > for X number of seconds. This is not a good idea if you have ever changing > data displayed/different variable input. As Michael said, it seems the > Drupal boost does a similar thing, but at application level (so it may be > slower)
A caveat here - mod_cache is NOT effective with pages that have dynamically caching information or when cookies are used. This is why I advised in my last post to use it for dynamically produced non cookie pages and 'on the fly' images that have static content (like product images stored as blob in a database). The reason is that mod_cache stores 2 files per 'page' - a file with the rendered source code and a file with the header info - including any cookie stuff. As said before if any application needs caching for PHP HTML-rendered code it is time to seriously look at code quality and / or server capacity. --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
