11–20 of 145 posts
Reading the comment threads on GitHub, some files get a TTL of 300, some get a TTL of 86400. The "why" is certainly an interesting question.
There are two hard problems in IT: cache invalidation, naming things and off-by-one errors.
You can eliminate the cache invalidation problem by not reusing old names for new things.
Earlier quoted context omitted.
You can eliminate the cache invalidation problem by not reusing old names for new things.
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.
It's been for example impossible to make files completely disappear from an open source repo without deleting the repo or contacting their support.
Reading the comment threads on GitHub, some files get a TTL of 300, some get a TTL of 86400. The "why" is certainly an interesting question.
I would guess GitHub is slowly cutting down on people (ab)using it for free file hosting. Files that are hit a lot probably get significantly longer cache timeouts.
There are two hard problems in IT: cache invalidation, naming things and off-by-one errors.