Standard caching in Radiant involves the web server talking to
Radiant. Basically Radiant looks around and says "ah, I have it here
already, here you go."
Static caching is where the web server comes into the room, sees the
page there and leaves without Radiant knowing about it. It doesn't
make a big difference if you are hosting one site, but if you have a
bunch of sites running on the same server, I think the latter is
awesome because it just means less memory being used by Ruby
processes. Besides that, you can then have your web server take the
static pages and compress them, which I would like to do...
-Chris
On 4-Oct-08, at 4:20 PM, Jay Levitt wrote:
Christopher Dwan wrote:
Hey, I just saw this on github!
http://github.com/tricycle/radiant-static-caching-extension
Has anyone used it? Is this 'production ready', i.e. safe to use?
I haven't seen any discussion about it..
I'm missing something.. how does this differ from page caching?
Jay Levitt
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
