I strongly agree with this. One thing I've discovered programmers
are universally poor at, it is dealing with time zones. DST was so
much fun at eBay twice a year. Let's move to a purely relative time,
then it doesn't matter whether all the machines are synchronized to
the same time server and timezone.
On Jul 12, 2007, at 5:16 AM, a. wrote:
Ticks are easy in .NEt, but I'm much more concerned about the
"meaning" of that specific time.
If my server runs DST but one of the clients is on CET, and the
client sends 2007-07-12 12:00 AM, what does it mean? 12:00 in DST
or CET?
We either should declare that absolute expiration should treated as
UTC, or get rid of it and use relative expirations.
