2014-07-11 13:30 GMT-03:00 Paul DeBruicker <pdebr...@gmail.com>: > Additionally I think its helpful to remember that timezones are political > constructs and so are completely arbitrary and open to change based on the > whims of political leaders e.g. > > https://en.wikipedia.org/wiki/Time_in_Russia#Daylight_saving_time > > So best keep them out of your code, near the presentation layer, as much as > possible as Stephan recommends.
Yeap, and using UTC whenever possible to have a "zero" point of reference. Even when using a predefined time offset would be possible. After reading W3's TR I mentioned before, I learnt there is a reason to store timezone information if you have to deal with dates and times in the future when using incremental time representations (like the ones used by most systems). In such case a change in DST. Regards, Esteban A. Maringolo
