From: Gregg N 

Mike N. wrote:
> On Sun, 18 Mar 2007 12:23:20 -0400, Gregg N 
> wrote:
>
>>>    8 AM in your local time zone is not the same time in UTC every day.
>>> The actual time depends on the relationship between localtime and UTC.
>>> That relationship changed.
>>>
>> What is the reason for storing the time as UTC instead of as local time,
>> given that local time is what is being scheduled?
>
>    That's a good question.  While I don't know what they actually did,
> often the data is placed into a central data store in which localtime has
> no meaning.    Especially when it is necessary to access the appointment
> from anywhere in the world.   So for Geo's example, they'd have to store as
> 08:00 EST .   But now what happens when 08:00 EST changes to  08:00 EDT
> after the fact?    At least it is easily correctible compared to the first
> example, but such problems may not have been obvious when the datastore was
> being designed.

That makes sense, I think. I hadn't considered that the client and the
server might be in two different time zones.

Gregg

--- BBBS/NT v4.01 Flag-5