On Thu, Oct 20, 2011 at 7:33 AM, Henning Brauer <lists-open...@bsws.de> wrote:
> * Janne Johansson <icepic...@gmail.com> [2011-10-20 15:11]:
>> What I meant was as you say, we can change the include file to say "use 64
>> bits for time" and recompile some apps, but if the database file format or
>> the over-the-wire formats don't support 64 bits for specifying time, you'd
>> be screwed anyway. That's why applications, formats and protocols need to
>> change, since many of them use 32 bits today.
>
> anything clean just uses time_t and is thus fixed by recompiling.
>
> now, reality check, there is way too much crap out there that makes
> dumb assumptions. but "many of them use 32 bits today" makes it sound
> like a) that was common and b) right. it isn't. certainly not b). time
> will tell us (oh the irony) about a).
Not a) for the two examples mentioned.
HTTP Expires header: ascii date string. Good until at least 9999...
NTP (from wikipedia):
Implementations should disambiguate NTP time using a knowledge
of the approximate time from other sources. Since NTP only works
with the differences between timestamps and never their absolute
values, the wraparound is invisible as long as the timestamps are
within 68 years of each other.
-N
