Re: [Task Scheduler API ]: Timezone handling

Not to comment on the proposal (which I certainly don't endorse), but please note that you've oversimplified timezones. There's something like a +13, there are a couple of +/- x:30, and there's at least one which is +x:15 or x:45. You also discount DST which is its own complicated mess.

This also requires an incredibly complicated database which most vendors won't manage to maintain. Conversely, it would be possible for a network connected application to actually get this information today, using a service like Internet time and date - http://www.timeanddate.com/time/map/


API in my opinion should only be created when they require information that an application is unlikely to be able to get correctly on its own without the UA's assistance.

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Received on Sunday, 25 August 2013 20:59:53 UTC