RE: Network Information Use Cases

Comments inline.

Thanks,
Dan

-----Original Message-----
From: jeanfrancois.moy@orange.com [mailto:jeanfrancois.moy@orange.com] 
Sent: Thursday, July 05, 2012 6:05 AM
To: tobie@fb.com; public-coremob@w3.org
Subject: RE: Network Information Use Cases

> -----Original Message-----
> From: Tobie Langel [mailto:tobie@fb.com]
> Sent: 05 July 2012 10:56
> To: MOY Jean Francois RD-ILAB-LON; public-coremob@w3.org
> Subject: Re: Network Information Use Cases
> 
> On 7/5/12 11:43 AM, "jeanfrancois.moy@orange.com"
> <jeanfrancois.moy@orange.com> wrote:
> 
> >I am aware of the fact that the current specification would not allow 
> >switching from one network to another, but still the fact of knowing
> of
> >which network we are currently on is of interest.
> 
> In order to reconsider including Network Info API in coremob level 1, 
> there needs to be compelling use cases where Network Info API _in its 
> current form_ is both necessary and sufficient. None of the use cases 
> you mentioned can be met using Network Info only. They all also
require
> a way to change the network.
> 
> --tobie

The current version of the specification does not answer the whole problem; Indeed, a way to make sure that a request goes through a specific interface (does not have to change the network) would be ideal.

Dan> Network Interface API is required for switching networks and checking signal strength. But Network Information API is also useful to enable the use cases like video adaptive streaming (e.g. SD on 3G, SD or HD on WiFi), and warning user to turn on WiFi before a big download or video streaming to save the purchased data quota.

Received on Thursday, 5 July 2012 18:50:55 UTC