3 ms·
Front-side HTTP caching is all well and good, but what do you guys do in the case when the returned content is (at least partially) user-contextual? Caching isn
by tomlu 13y ago
Front-side HTTP caching is all well and good, but what do you guys do in the case when the returned content is (at least partially) user-contextual? Caching isn't really going to help you in these cases.
- mattrobenolt 13y agoObviously you can't cache everything. Hence why we still have 15k/s that are hitting out backends. There are lots of more complicated things we can do with ESI if we really wanted to get into it.
- adamauckland 13y agoI'm guessing they cache as much as they can here too https://docs.djangoproject.com/en/1.6/topics/cache/#template-fragment-caching https://docs.djangoproject.com/en/1.6/topics/cache/#template...
- mattrobenolt 13y agoTemplate fragment caching is not a good thing. We don't do this anymore. If you have to cache your template fragments, I generally think you're doing something wrong. Gonna have a bad time.