🚀 go-pugleaf

In article <3824@nigel.udel.EDU> new@udel.edu (Darren New) writes:
>  At the file server end, the server would do an
>Examine(), use local preferences to translate the DateStamp to UTC,
>send the packet.  The client would get the packet, convert back from
>UTC to local time using the client's preferences, and all is well.
>I still think things should all be stored in local time.

This won't work.  I currently have on my floppy two files that were
created 60 minutes apart, but they both correctly say 29-Oct-89 at 1:30am.

If you have an OS that understands both GMT (UCT) and local time, there
is no way to store the correct date/time unless it is in GMT.  If you store
only local time, anything between 1:00am and 2:00am on the last Sunday
in October can be interpreted as Standard time or Daylight Savings time.
And on the first Sunday in April, any local time between 2:00am and 3:00am
will be illegal.

We want a format that stores the date/time as a monotonically increasing,
non-discontinuous value.  Local time just doesn't cut it.
-- 
Joe Smith (408)922-6220 | SMTP: JMS@F74.TYMNET.COM or jms@gemini.tymnet.com
McDonnell Douglas FSCO  | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms
PO Box 49019, MS-D21    | PDP-10 support: My car's license plate is "POPJ P,"
San Jose, CA 95161-9019 | narrator.device: "I didn't say that, my Amiga did!"