Re: [Task Scheduler] Can we really remove TimezoneDirective argument?

Hi Mounir, please see my in-line response.

----- Original Message -----
> From: "Mounir Lamouri" <mounir@lamouri.fr>
> To: "Christophe Dumez" <ch.dumez@sta.samsung.com>, "Gene Lian" <clian@mozilla.com>, public-sysapps@w3.org
> Cc: "Marcos Caceres" <mcaceres@mozilla.com>
> Sent: Monday, November 18, 2013 10:09:50 PM
> Subject: Re: [Task Scheduler] Can we really remove TimezoneDirective  argument?
> 
> This API might be hard to use for an alarm clock application but it is a
> fairly limited use case. I can't actually think of any other kind of
> applications that would set tz-agnostic alarms. Also, given that most
> calendars events can be defined by an UTC time, I think using this API
> for a calendar application should be mostly fine.

I support making this API as simple as we can (i.e. don't need
to consider the complex tz/DST effects), because that's the main
principle of defining APIs: generic enough to be standarizable.

However, it's very obvious that the Alarm Clock App is going to
be a main client of this API. If we cannot find a good way to
reflect the system timezone change, then this API cannot
independently work for the Alarm Clock App scenario, though.

Btw, are we really sure the Calendar app doesn't need to adjust
the tasks by listening for the dynamic timezone changes?

For example, if I set an activity at 2013/12/31 11:59pm to
prepare to celebrate the New York, then I would expect it will
alert me at 11:59pm of that local time no matter which timezone
I'm currently in.

That is, all the issues happening in the Alarm Clock App should
also be valid in a Calendar App. Right?

Gene

Received on Friday, 22 November 2013 04:03:01 UTC