We do the same (albeit CET based). The tricky part is then in encapsulating API's, as queries and results have to account for this time-shifting. It gets even worse when you have to depict stuff in a XY-chart made for 24h, not 23 nor 25.
/Casper PS: Does anyone want to join me in forming a foundation against DST? lol On 30 Sep., 14:45, Robert Casto <[email protected]> wrote: > I got a message from Sun today saying I should get their tool to make sure > my machines are all having their times managed properly. > > https://communications2.sun.com/servlet/cc6?kmgQUCAQSVJHklhQjhILjlxnu... > > I find this a loosing proposition. It is nearly impossible to get machines > to agree on what time it is. > > I like to use the database to dictate the time a transaction happens. It is > a controlled environment and much easier to keep in sync. I set it to > Greenwich Mean Time (GMT) and then never change it. I translate that > timestamp to whatever time I need at the application level. > > How does everyone else handle time? > > -- > Robert Castowww.robertcasto.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
