131–140 of 145 posts
Earlier quoted context omitted.
No, we are where we should have always been: > GET /file/latest HTTP/1.1
Sure... but their CDN is caching the results for /file/latest, so they'd either have to handle cache expiry differently or the same bug would happen.
> This response is only cacheable if indicated by a Cache-Control or Expires header field.
There are two hard problems in IT: cache invalidation, naming things and off-by-one errors.
There are actually only two hard problems in computer science: 0) Cache invalidation 1) Naming things 5) Asynchronous callbacks 2) Off-by-one errors 3) Scope creep 6) Bounds checking
So this list is too bloated for the joke to work well, I think. Even before we talk about how off-by-one gets ruined this way.
There are two hard problems in IT: cache invalidation, naming things and off-by-one errors.
There are actually only two hard problems in computer science: 0) Cache invalidation 1) Naming things 5) Asynchronous callbacks 2) Off-by-one errors 3) Scope creep 6) Bounds checking
Earlier quoted context omitted.
That doesn't solve cache invalidation; that just means you're always invalidating the cache even in cases where you don't actually want to.
Content addressing causes the name to change only when the content changes, which also means the name doesn't change if the content doesn't change, this by definition you don't have spurious cache invalidations
Or what if your CSS change just deletes some unused classes... it'd be fine for users to keep the old version until it expires. If you rename the resource you'll be causing a lot of users to wait unnecessarily. Not a huge problem, unless you're Meta or Google.
And so on.
When people say cache invalidation is hard it's best to believe them, because it is.
Earlier quoted context omitted.
I’m not fine with latest not actually being latest. That defeats the point of the URL.
There's a hard limit on that - the speed of light. You can't know what the actual latest is, only some cached value. The actual value may have changed while the message is in flight
Earlier quoted context omitted.
I’m not fine with latest not actually being latest. That defeats the point of the URL.
I get the issue but I do strongly feel that you should expect http resources to be cached. It's so common of a thing expecting it to never be cached is unreasonable as a design. I would expect the headers to make this clear, however.