W3C home > Mailing lists > Public > public-device-apis@w3.org > February 2013

Re: Liaison statement from OMA on network efficiency

From: Tobie Langel <tobie@fb.com>
Date: Tue, 12 Feb 2013 13:27:44 +0000
To: "hi-yokota@kddi.com" <hi-yokota@kddi.com>, "SULLIVAN, BRYAN L" <bs3131@att.com>, Dominique Hazael-Massieux <dom@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>, "Frederick.Hirsch" <Frederick.Hirsch@nokia.com>
CC: Mohammed Dadas <mohammed.dadas@orange.com>
Message-ID: <F9981AFB970564408FEB7DFCF62D4408471213E2@PRN-MBX01-4.TheFacebook.com>
On 2/7/13 6:30 AM, "hi-yokota@kddi.com" <hi-yokota@kddi.com> wrote:

>Hi Bryan, Dominique and all,
>
>I fully support Bryan's opinion and would like to make the network more
>visible and easy to use for WebApps for it to be able to use network
>resources more efficiently. Privacy and security issues are very
>critical; therefore must be handled carefully, but we have several tools
>to manage them. OMA, GSMA and 3GPP are working on network efficiency in
>different forms and areas. W3C should interwork with them since network
>efficiency is achieved by end-to-end. I'm wondering how we can move it
>forward...

I wrote to length about this already. Getting developers to care about the
network implies you either have a carrot or a stick.

Here the stick is a way for end-users to become aware of which website /
web app is draining their battery. This implies lobbying user agent
vendors to surface this information to the user.

The carrot is all about providing Web developers with APIs that don;t
exist know but would be awesome to have (and that let you save bandwidth).
For example, an API which would let developers download or upload large
amounts of info in the background would be awesome (use cases: upload
pics, download the weekly edition of an online magazine, etc.). Currently
this has to be done by the application itself, when it is in front of the
user's eye. A great API to do this would allow requesting a background
update whenever this is convenient (e.g. on wifi over the next 24 hours).
The user agent is in charge of the whole process and can do all bandwidth
optimization it wants to. The developer gets a new API. The user gets a
phone that lasts longer and better user experience.

There are plenty of other API that could help with your goal to lower
network congestion and that don't imply actually exposing network data
most developers do not understand or have any incentive to use, e.g.: HTTP
diffs, APIs to prefetch resources, bulk XHR requests, fixed AppCache, etc.

So to answer your question about how to move forward, I suggest you look
at ways to give carrots to developers that can benefit the network. We'll
all be better off for it. :)

--tobie
Received on Tuesday, 12 February 2013 13:28:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 12 February 2013 13:28:16 GMT