the difference here is that the html files are served by nginx, before django is event touched. Removing Django from the equation (and fastcgi or modpython or whatever nginx is proxying too) is where the speedup comes from. This isn't "caching" as much as it is fairly smoothly making certain areas of the site static html.
Yes, that's exactly my point. Is this the first approach that does this within the Django framework?
That is exactly how page caching in Rails works, and has been implemented for two years. It seems like Django's idea of "page caching" is equivalent to Rails' "action caching".
i see your point. i would assume someone else has done this before in django, but regardless, i thought it was interesting as i haven't seen something like this as easily accessible for us django people.
