W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2011

Re: Network Information API published as FPWD

From: Harald Alvestrand <harald@alvestrand.no>
Date: Tue, 14 Jun 2011 11:56:56 +0200
Message-ID: <4DF73068.4010805@alvestrand.no>
To: Dominique Hazael-Massieux <dom@w3.org>
CC: public-device-apis@w3.org
Hmm. This worries me.

This draft is mercifully short, but is also likely to be so simplistic 
as to be less than useful.

The API is not able to represent:
- Boxes with multiple, simultaneously operational interfaces. This 
occurs frequently with laptops, and is theoretically possible even on 
Android.
- The operational state of an interface. An interface may be absent, 
present-but-disabled, present-but-unconnected, or present-and-connected.
- Any handle to get more information about the interface.

This simplicity may be justified if the purpose is to designate the type 
of interface that the device is currently routing packets out of in the 
absence of specific other information (the default route), but then the 
specification needs to say that this is what the API is supposed to 
represent.

WRT to the multiple-online-event issue: For video-using applications, 
the switch from online(2g) to online(3g) to online(wifi) is definitely 
of interest as a trigger for reprobing available bandwidth.

On 06/07/11 18:59, Dominique Hazael-Massieux wrote:
> Hi,
>
> The First Public Working Draft of our Network Information API has just
> been published: http://www.w3.org/TR/2011/WD-netinfo-api-20110607/
>          The Network Information API provides an interface for Web
>          Applications to access the underlying network information
>          (connection info) of the device.
>
> Feedback and comments welcome!
>
> Dom
>
>
>
>
Received on Tuesday, 14 June 2011 09:57:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:21 GMT