Re: [web-alarms] Remove timezone support from Task Scheduler API

+1

Very clear reasoning.

As mentioned in the F2F, IMHO 2 API's would make sense: a task scheduler
with no TZ, and then a separate calendar API with TZ and recurrence support
(when it comes).

Best regards,
Zoltan


On Mon, Sep 2, 2013 at 11:05 AM, Christophe Dumez
<ch.dumez@sta.samsung.com>wrote:

> **
> Hi,
>
> It was proposed during the last SysApps face to face in Toronto to remove
> timezone support from the Task Scheduler API [1].
> This would essentially mean removing the TimezoneDirective [2] from the
> API and pass a number of second since epoch to schedule a task instead of
> an EcmaScript Date (e.g. by using "Date.now() + n").
>
> The change was proposed for several reasons:
> - The TimezoneDirective is not very clear, may be confusing to the
> developers and makes the API more complex,
> - The current timezone support is not sufficient to handle calendar use
> cases anyway since you cannot explicitly specify which timezone to use,
> - The Date object may be removed from Web IDL [3] as its use was
> discouraged on es-discuss [4].
>
> I am sending this message to the mailing list to gather broader feedback
> before updating the specification draft. Please let us know how you feel
> about this change.
>
> [1] http://www.w3.org/2012/sysapps/web-alarms/
> [2] http://www.w3.org/2012/sysapps/web-alarms/#timezonedirective
> [3] https://www.w3.org/Bugs/Public/show_bug.cgi?id=22824
> [4] http://esdiscuss.org/topic/frozen-date-objects
>
> Kr,
>   --
> Christophe Dumez - Samsung Telecommunications America
>