Hi, On Tue, Jan 21, 2014 at 5:43 AM, Wang, Shiliu <shiliu.w...@intel.com> wrote:
> Hi, Kenneth > > > > Thanks for the comments. > > > > 1. It’s not that notification is not working in background, it’s no > service worker like mechanism to support it. And it’s not related to no > matter how we implement the notification, in another word, any solution for > notification needs service worker to work well in background. > So basically you say that the issue can be fixed by just extending the current notification system, but if you read the email on SysApps you will see that it is not that clear at all and many possible solutions are being discussed, especially as the wrong solution can have a very negative effect on the battery. The email looks at local and remote notifications, and considers taskScheduler, extending the current notification system, as well as the Push API. > 2. It’s not that notification is absolutely not working when app > is in background, it is just timer not working. So if an application is > timely pulling information from web server, it will not work currently, but > if the web server is pushing message via persistent connection, it will > work even the app is in background. > And what if the application is not running? Or we should just hide our applications? which can waste memory and kill the battery life? 3. I agree that participate in Google’s notification solution is > good. In the other side, as I already described in the “Intent to > Implement”, the notification will be missing for a long time for upstream, > thus Google is aiming to change spec. So as I proposed in the intent is to > implement current spec with minor effort first, and then see how upstream > goes. > So you suggest we implement something that we have to support for the next 10 years if people starts adopting it, that you *know* will be changed from its current form, that might have a very negative effect on battery usage and performance (if taking up memory for other apps). It seems to me like all the wrong reasons to implement something and something which could end up being very costly for us, while not really solving any real issues for web developers as we didn't fix the core issues. I would be 100% OK with implementing something if we knew that it would not have negative effects in the future, that we can support it going forward and/or if there was a clean way to fix it. Right now there is not and I have hereby given my not lgtm and suggest that we tackle the real issues in cooperation with other browser vendors in the respective working groups. If other people disagree feel free to overrule me, but consider yourself warned. If you manage to solve all the core issues pointed out, feel free to raise this issue again, or if there is some subset that can be implemented without any issues; but I want proof to back up such claims. Kenneth > > > Thanks, > > Shiliu. > > > > > > *From:* Crosswalk-dev [mailto: > crosswalk-dev-boun...@lists.crosswalk-project.org] *On Behalf Of *Kenneth > Rohde Christiansen > *Sent:* Monday, January 20, 2014 8:40 PM > *To:* Balestrieri, Francesco > *Cc:* <crosswalk-dev@lists.crosswalk-project.org> ( > crosswalk-dev@lists.crosswalk-project.org) > *Subject:* Re: [Crosswalk-dev] Summary of "Intent to Implements", ww 03 > > > > With regard to "[Android] Standard Web notification API for xwalk", I > have some concerns. > > > > I am not sure now much sense it makes to implement as it won't work when > the apps are in the background. > > > > As Google are looking into solving this (check the email by John Mellor on > SysApps ML etc.) I think it would be nice if the interested parts > participate in that discussion and comes up with a solution which works for > us as well as Chrome for Android. > > > > Kenneth > > > > On Mon, Jan 20, 2014 at 6:15 AM, Balestrieri, Francesco < > francesco.balestri...@intel.com> wrote: > > *Title* > > *Originator* > > *Sent* > > *Comments/Status* > > *Feature* > > *Release* > > *Ref Email* > > [Runtime Model] System event > > changbin.shao at intel.com > > 11/21/2013 > > agreed through internal discussion to run the main document > post-installation. No LGTM but considered OK > > XWALK-1 > > Crosswalk-4 > > > https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2013-November/000484.html<https://www.google.com/url?q=https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2013-November/000484.html&sa=D&usg=ALhdy292Bj2YnAj3YSylU2SmRbqN-Oaayw> > > SplashScreen API for xwalk based application > > junmin.zhu at intel.com > > 12/19/2013 > > Implementation ongoing according to Kenneth's spec, assumed LGTM > > XWALK-637 > > Crosswalk-4 > > > https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2013-December/000677.html<https://www.google.com/url?q=https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2013-December/000677.html&sa=D&usg=ALhdy2-NdVgDT-hwv2n64gMspP2J1cXVBQ> > > [Android] Standard Web notification API for xwalk > > shiliu.wang at intel.com > > 12/23/2013 > > LGTM from Yonghseng > > XWALK-94 > > Crosswalk 4 > > > https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2013-December/000736.html<https://www.google.com/url?q=https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2013-December/000736.html&sa=D&usg=ALhdy28Tk_gpXwJw4E6HKNkGgNgGkEtaMw> > > Build WebApps with Eclipse for Crosswalk on Android > > donna.wu at intel.com > > 12/24/2013 > > Discussion on ML, concerns on making IDE a required tool > > XWALK-636 > > Crosswalk-5 > > > https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2013-December/000744.html<https://www.google.com/url?q=https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2013-December/000744.html&sa=D&usg=ALhdy2-DQfc9qPskCFE2Gj_lH8JgrVnk8w> > > IAP support for Android > > deqing.huang at intel.com > > 1/1/2014 > > Discussion ongoing > > XWALK-594 > > Crosswalk-5 > > > https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2014-January/000812.html<https://www.google.com/url?q=https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2014-January/000812.html&sa=D&usg=ALhdy29Vkbxxpg8U-WBRuTy2CBniG5assg> > > [Tizen] Application API > > xiang.long at intel.com > > 1/6/2014 > > Sakari asked to put this on hold for now > > XWALK-810 > > Crosswalk-5 > > > https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2014-January/000825.html<https://www.google.com/url?q=https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2014-January/000825.html&sa=D&usg=ALhdy2-HfrCOu9NIa8DJhsujj_9PDYgyig> > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~ > > Francesco Balestrieri > > Program Manager > > +358407586772 > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > Intel Finland Oy > Registered Address: PL 281, 00181 Helsinki > Business Identity Code: 0357606 - 4 > Domiciled in Helsinki > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > > > _______________________________________________ > Crosswalk-dev mailing list > Crosswalk-dev@lists.crosswalk-project.org > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev > > > > > > -- > Kenneth Rohde Christiansen > Web Platform Architect, Intel Corporation. > Phone +45 4294 9458 ﹆﹆﹆ > -- Kenneth Rohde Christiansen Web Platform Architect, Intel Corporation. Phone +45 4294 9458 ﹆﹆﹆
_______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
