W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2013

RE: Web Alarm API - idiomatic check

From: Domenic Denicola <domenic@domenicdenicola.com>
Date: Wed, 8 May 2013 18:10:56 +0000
To: Marcos Caceres <w3c@marcosc.com>, public-script-coord <public-script-coord@w3.org>
Message-ID: <B4AE8F4E86E26C47AC407D49872F6F9F7EF88E91@BY2PRD0510MB354.namprd05.prod.outlook.com>
The futures usage looks reasonable, but there still seems to be a lot of event-handler cruft left over? Especially in the opening example?

One thing that confused me is the repeated "If an error occurs" verbiage. How could an error occur? The phrase "error" only occurred in the document inside those phrases, so I'm not sure what's going on there.

________________________________________
From: Marcos Caceres [w3c@marcosc.com]
Sent: Wednesday, May 08, 2013 13:54
To: public-script-coord
Subject: Web Alarm API - idiomatic check

Hi,
The SysApps WG would appreciate if the JS folks could take a look at:
http://web-alarms.sysapps.org/
(it's nice and small, promise)


And provide us some feedback on the idiomatic aspects (i.e., to make sure it isn't "another crap W3C API").

A disclaimer: The API's name is terrible, we know that (should be called Web Cron or Web Scheduled Tasks or something less awful). We've tried to use Futures, but we are new to them.

Anyway, any/all, comments welcome.  If you want to file bugs directly (or see what bugs we have open):
https://github.com/sysapps/web-alarms/issues/ (https://github.com/sysapps/web-alarms/issues/new)

Kind regards,
Marcos
Received on Wednesday, 8 May 2013 18:11:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:49 UTC