4 ms·
You don't implement HTTP caching, except in very specific cases. You cache generated data where you need it. This is 1) Easy to add later, 2) Doesn't sacrifice
by pifflesnort 14y ago
You don't implement HTTP caching, except in very specific cases.
You cache generated data where you need it. This is 1) Easy to add later, 2) Doesn't sacrifice the flexibility of being able to recompose that data on-demand, and 3) Doesn't require a bunch of complex front-end infrastructure to support.
- Tomte 14y agoOf course "you don't implement caching". I think it was clear that I was talking about designing a cache-aware application. Cf. http://www.mnot.net/cache_docs/ http://www.mnot.net/cache_docs/.
- pifflesnort 14y agoYes, and I was talking about implementing caching of components used to compose the pages and API responses, not a full HTTP cache tier that has to be placed in front of your application.
- Tomte 14y agoOkay, then I misunderstood where you were getting at. My fault.