- From: Tobie Langel <tobie@fb.com>
- Date: Wed, 18 Jul 2012 17:29:02 +0000
- To: "SULLIVAN, BRYAN L" <bs3131@att.com>, Core Mobile <public-coremob@w3.org>
Thanks for the feedback, Bryan. On 7/18/12 7:20 PM, "SULLIVAN, BRYAN L" <bs3131@att.com> wrote: >One of the key use cases we are exploring is opportunistic use of >existing network connections, to avoid apps from needing to create a new >network connection for transfer of data that can wait until there is some >connection established for other purposes (i.e. by some other app or >device function). Giving developers tools and guidelines to help reduce >RRC (radio resource control) layer chatter on mobile networks is one of >the goals of the GSMA's Application Network Efficiency (ANEFF) project >and the Network Friendly App and Webapp Community Group [1]. Currently a >lot of very short connections are used by apps, >asynchronously/uncoordinated. The navigator.connection interface as well >as the currently existing navigator.onLine interface will hopefully be >valuable in enabling developers to use network connections more >opportunistically, for data transfers that can be delayed until an >opportunity arises. I'm not sure I understand how the Network API (in its current state) would help here. Care to clarify? >Related to that use case goal, as part of the wiki it would be useful to >explain the relationship of the navigator.connection interface with the >navigator.onLine interface, and point to experience testing with the >current implementations of the interfaces. Please feel free to add stuff to this page. It's a wiki, after all. ;-) --tobie
Received on Wednesday, 18 July 2012 17:29:28 UTC