Quarantine this entry

Comments (2)

Hi James...I was curious about using milliseconds as the unit of
measure for expiration. Are there use cases where sub-second
expiration is important?And in those cases where such precision in
required, what happens if the clocks on the two systems are out of
sync? Do you get in a position where the receiver may think the
feed is valid, and the feed originator thinks not?

The choice of milliseconds was to provide the greatest amount of
flexibility for implementors. The max-age is always calculated
against the exact moment specified in the atom:updated or
atom:published elements. There is no accounting for syncronization
variances and yes, there is the possibility that a receiver could
think that the feed metadata is still valid. Mitigating such cases
is out of scope for the expiration spec.