- From: SULLIVAN, BRYAN L <bs3131@att.com>
- Date: Thu, 24 May 2012 13:37:20 +0000
- To: Ms2ger <ms2ger@gmail.com>
- CC: public-webapps <public-webapps@w3.org>
Sorry, cut & paste error: the spec is at: http://dvcs.w3.org/hg/push/raw-file/default/index.html Thanks, Bryan Sullivan -----Original Message----- From: SULLIVAN, BRYAN L Sent: Thursday, May 24, 2012 6:02 AM To: 'Ms2ger' Cc: public-webapps Subject: RE: Push API draft uploaded Thanks for the comments. I updated the spec: - define what happens when url is omitted - remove [NoInterfaceObject] - define readyState as a unsigned short (that was what was meant in the first place) - fix cut/paste errors I still have to find the source of "resolve a url" as that's a function I borrowed from EventSource. Latest version is at http://dvcs.w3.org/hg/push/raw-file/default/index.htm Thanks, Bryan Sullivan -----Original Message----- From: Ms2ger [mailto:ms2ger@gmail.com] Sent: Thursday, May 24, 2012 12:33 AM To: SULLIVAN, BRYAN L Cc: public-webapps Subject: Re: Push API draft uploaded On 05/24/2012 09:14 AM, SULLIVAN, BRYAN L wrote: > Thanks to the inestimable help of the W3C staff I am now plugged into > the mercurial mainline and have uploaded the first stab at the Push > API > http://dvcs.w3.org/hg/push/raw-file/default/index.html A couple of notes on the WebIDL: * PushManager has |PushService requestRemotePermission ([Optional] DOMString url);|, should be ... (optional DOMString url), though the spec doesn't appear to define what happens when url is omitted; same for checkRemotePermission. * There does not appear to be a need to make PushManager and PushService use [NoInterfaceObject], so please remove that. * PushService.readyState is a DOMString, but the spec defines it to return the unsigned short constants CONNECTING/OPEN/CLOSED. Please get rid of the constants. "The requestUrl attribute must return the absolute URL where the webapp server can send Push service messages to this webapp." should probably refer to |serviceUrl|, not |requestUrl|. A reference to DOM4 for the DOMError interface should probably be added. Also, the "resolve a url" cross-reference is broken. HTH Ms2ger
Received on Thursday, 24 May 2012 13:38:31 UTC