W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2014

RE: Push API and Service Workers

From: Shijun Sun <shijuns@microsoft.com>
Date: Thu, 16 Oct 2014 21:52:25 +0000
To: Martin Thomson <martin.thomson@gmail.com>, John Mellor <johnme@google.com>
CC: Anne van Kesteren <annevk@annevk.nl>, Domenic Denicola <domenic@domenicdenicola.com>, Nikhil Marathe <nsm.nikhil@gmail.com>, "Jonas Sicking" <jonas@sicking.cc>, public-webapps <public-webapps@w3.org>
Message-ID: <b5770af4b9ba4333981975f8b3b915d7@BLUPR03MB405.namprd03.prod.outlook.com>
On Thursday, October 16, 2014 11:46 AM, Martin Thomson wrote
> If the push message is being used to deliver a call notification, that sort of delay will definitely be noticed.  And I'm assuming that you've tested on a high end Nexus or something like that.  Add the latencies involved in waking an idle device and that turns into a very long post-dial delay.  People abandon calls for that sort of delay.
> Not saying that you are doing it wrong or anything, but just trying to set the right expectations.

The RTC scenario is listed explicitly as one of the use cases in the Push API wiki [1].  I expect there is enough interest in the group.  Should we allocate some cycles in TPAC to figure out details of the E2E flow?

[1] http://www.w3.org/2008/webapps/wiki/Push_API

Received on Thursday, 16 October 2014 21:52:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:31 UTC