Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


I actually don’t. Git already has a file on the filesystem. Serving a plain file is as close to caching as you are going to get.


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


Guess we may as well throw our handa up in the air then and set a 14 year cache ttl.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: