Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Newsgroups: comp.sources.bugs
Subject: Re: Flame: Problem with zoo: restoring times
Message-ID: <5868@bsu-cs.UUCP>
Date: 23 Feb 89 17:16:43 GMT
References: <2884@mhres.mh.nl> <5930001@eecs.nwu.edu> <3453@sugar.uu.net> <1989Feb19.134220.29438@gpu.utcs.toronto.edu> <3465@sugar.uu.net> <1989Feb20.183931.13918@gpu.utcs.toronto.edu> <5798@bsu-cs.UUCP> <7803@chinet.chi.il.us> <9695@smoke.BRL.MIL>
Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 18

In article <9695@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
writes:
     An archive with UTC0 embedded in it has a universal (or at least
     planetary) meaning for its time stamps, which enables each site to
     deal only with its own time-zone problems independently of the
     other.

Note that the current scheme, of storing local time as well as
timezone, implicitly stores both UTC and the local time of the user
creating the archive.  If UTC is not available, then it only stores the
user's local time.

Under the same conditions, a scheme storing only UTC fails completely.

(I don't know the difference if any between UTC0 and UTC.)
-- 
Rahul Dhesi         UUCP:  <backbones>!{iuvax,pur-ee}!bsu-cs!dhesi
                    ARPA:  bsu-cs!dhesi@iuvax.cs.indiana.edu