←back to thread

Tower Defense: Cache Control

(www.jasonthorsness.com)
58 points jasonthorsness | 1 comments | | HN request time: 0.204s | source
1. nixpulvis ◴[] No.44008779[source]
I've always wondered if it would be worth the effort to display information to the user to indicate that their request was stale and that they'll need to refresh again? 15s is pretty quick, but how do caching schemes work when users need to know when to use their time refreshing and checking the results. Alternatively, I'd be interested to read about the architecture of a modern always fresh caching scheme.