Re: Clock skew and the importance of clock synchronization in HTTP servers.
Joel N. Weber II (devnull@gnu.ai.mit.edu)
Fri, 12 Sep 1997 15:28:10 -0400 (EDT)
a) expire immediately or never cache
b) expire in 15 minutes to an hour, which is essentially the same as
"immediate" but reduces some flash effects from people sharing the
same proxy.
c) expire on some date in the future (1 day/week/month), which is
typically used for resources that rotate content periodically.
If these cases are the only ones that we care about, then we can
solve these problems without having the clocks syncronized.