On 03/01/2017 18:38, Cyrus Daboo wrote:
Hi Stewart,
--On January 3, 2017 at 6:30:19 PM +0000 Stewart Bryant
<stewart.bryant@xxxxxxxxx> wrote:
Only the UI needs the TZ information, the machine can operate just fine
with any timescale. That is you present the time in local time, but
operate in global time, and this is definitely an application that will
not care about leap seconds.
No that simply does not work. Repeating events or alarms may not
involve any UI at all, but the device may need to trigger those at a
specific local time - that means time zone information has to be taken
into account somewhere. This is a crucial fact of any calendaring and
scheduling system that those of us who have been using iCalendar
(RFC5545) fully appreciate.
Hi Cyrus,
I think that depends on what you consider to be the infrastructure and
what you consider the application. I would like to see the CPU clocks,
and in particular the time transfer protocols just work on non-jumpy
constant-duration-second time since that has to scale from
sub-femtoseconds to millennia with sub-femtosecond accuracy without
glitching and with unambiguous duration measurements.
If we distribute time in the infrastructure as non-jumpy
constant-duration-second time , then the iCal system can surely do the
conversion to/from whatever format the human needs? Whether it talks to
itself in human time or machine time is for those of you that design
iCal to determine, but it sounds from what you say that it talks to
itself in human time. Whether it does the conversion from machine time
to human time, or whether the OS does it for outside the scope of the
point I am making.
- Stewart