From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_021A_01C76957.9671A550
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

   Local time is not always what is being scheduled.  I have events =
scheduled for when I travel to other time zones or meetings between =
people in multiple time zones.  When people in other time zones check my =
schedule they want to see the actual times of the events not what would =
be the local time of the time zone where I entered the appt.

   This is a key reason why computers use UTC at all.  If you didn't =
want times to have meaning throughout the world you could always use =
local time.  I'm sure you will still find some bad software that does =
this which many users that never move time zones wouldn't miss.

Rich
  "Gregg N"  wrote in message =
news:45fd6769{at}w3.nls.net...
  Rich wrote:
  >    8 AM in your local time zone is not the same time in UTC every =
day. =20
  > The actual time depends on the relationship between localtime and =
UTC. =20
  > That relationship changed.
  > =20

  What is the reason for storing the time as UTC instead of as local =
time,=20
  given that local time is what is being scheduled?

  Gregg
------=_NextPart_000_021A_01C76957.9671A550
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable








   Local
time is not always =
what is being=20
scheduled.  I have events scheduled for when I travel to other time =

zones or meetings between people in multiple time zones. 
When = people=20
in other time zones check my schedule they want to see the actual times = of the=20
events not what would be the local time of the time zone where I entered = the=20
appt.
 
   This is a
key reason why =
computers use=20
UTC at all.  If you didn't want times to have meaning throughout =
the world=20
you could always use local time.  I'm sure you will still find some = bad=20
software that does this which many users that never move time zones = wouldn't=20
miss.
 
Rich

  "Gregg N" <invalid{at}invalid.invalid>">mailto:invalid{at}invalid.invalid">invalid{at}invalid.invalid>
= wrote in=20
  message news:45fd6769{at}w3.nls.net...Ri=
ch=20
  wrote:>    8 AM in your local
time zone is not =
the same=20
  time in UTC every day.  > The actual time
depends on the=20
  relationship between localtime and UTC.  > That =
relationship=20
  changed.>  What is the
reason for storing the time =
as UTC=20
  instead of as local time, given that local time is what is being=20
  scheduled?Gregg

------=_NextPart_000_021A_01C76957.9671A550--

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