- From: <nicolas.mailhot@laposte.net>
- Date: Wed, 8 Mar 2017 14:17:53 +0100 (CET)
- To: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Cc: Joe Touch <touch@isi.edu>, Wesley Oliver <wesley.olis@gmail.com>, Jim Reid <jim@rfc1035.com>, ietf-http-wg@w3.org
On 2017/03/08 19:08, nicolas.mailhot@laposte.net wrote: > Never never advise anyone to store any datetime in local time, that's a false simplification that always result in long-term problems, with people confusing current local time with past local time with remote local time, pilling up badly thought workarounds, and making mistakes. > > Any sane app stores in UTC ot UT with local time conversion done in the UI (with the UI making sure which local time is used is clear to the user). | In general, this is extremely important and correct. But there's an | exception. If e.g. a meeting is at 3pm local time in some location, | independent of daylight saving time, then you better save that fact as | such, without trying to use UTC and friends. Even then you absolutely do want to save it in UTC (and display it in local time), otherwise you'll have problems as soon as you invite someone who usually lives in another country. Because *his* user agent will interpret local time as *his* local time, the user or the software will then attempt to convert to *your* local time, and botch everything up. -- Nicolas
Received on Wednesday, 8 March 2017 13:18:23 UTC