On Wed, Feb 8, 2012 at 10:17 AM, Ed Leafe <[email protected]> wrote: > On Feb 8, 2012, at 10:42 AM, Fred Taylor wrote: > > > But getting the user's local time is not the problem, it's posting things > > according to the application's time that's the issue. Kind of hard to > > explain (hard enough keeping it straight in my head!) with all the > > different app requirements, users from multiple locations, etc. > > I've done many calendaring apps, and there is one rule which you > should never break: use UTC for *everything*, and only convert to local > time for display. Internally all datetimes should be in UTC - no > exceptions! It doesn't matter if the user's machine is in one time zone, > the server in another, and the report generated in a third: UTC is UTC in > all locations. > > > Ed I agree 1000%. But these apps were originally developed 18 years ago. No reason to think of such things then. It's amazing they were even Y2K compliant!
Fred --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAJCBksqGn-k0bKHbRhJsOK_bGaf_+1ugnbi3emnz=le3u6x...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
