3 ms·
While you’re right in theory, it doesn’t always work in practice. Some systems fail to respect caching headers. Further, in my experience, intermediate caches
by SkyPuncher 3y ago
While you’re right in theory, it doesn’t always work in practice. Some systems fail to respect caching headers.
Further, in my experience, intermediate caches are mostly useless for non-binary product data. Either you need to make a round trip or you don’t. Sure, you can cache and return “not changed”, but you still get the latency. Just returning the data often isn’t much slower.
POST avoids all of those issues by pretty much saying “give us what we neeed every time”
- thejazzman 3y ago> Some systems fail to respect caching headers. Don't we call those bugs? http has a pretty well defined spec?
- SkyPuncher 3y agoCustomers don't care what's defined in the spec. They care how it works.
- jrochkind1 3y agoBy that logic, would you write a web site where every link was actually a POST unless it was to "static content"? That would be a disaster, no? I guess the person I was replying to, and you, were talking about Javascript API calls rather than ordinary HTML executed by a "browser". It still seems like a wrong idea to me, but if this is what you do on actual apps and have success, I guess that's a thing.