I just don't see the point to this kind of stuff.. =/
For high traffic apps, Varnish is the answer as you don't hit the application layer.
If you think that's too complicated, try nginx-memcached - also an excellent solution.
If not that, try django's template caching with memcached - also extremely fast but will hit the application layer.
If you're in some shared hosting environment (you probably are too small still to warrant this kind of aggressive caching on static assets - but hey, efficiency never hurt anybody :P) without access to memcached, use django's cache backend with a file based cache. It's almost 100% as what this does and you don't have any additional overhead.
Beats me why people are re-inventing the wheel - or am I missing something ?
For high traffic apps, Varnish is the answer as you don't hit the application layer.
If you think that's too complicated, try nginx-memcached - also an excellent solution.
If not that, try django's template caching with memcached - also extremely fast but will hit the application layer.
If you're in some shared hosting environment (you probably are too small still to warrant this kind of aggressive caching on static assets - but hey, efficiency never hurt anybody :P) without access to memcached, use django's cache backend with a file based cache. It's almost 100% as what this does and you don't have any additional overhead.
Beats me why people are re-inventing the wheel - or am I missing something ?