cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ken Wallis <>
Subject Re: w3c network information api shelved
Date Thu, 20 Feb 2014 00:12:43 GMT
Standards are certainly valuable, when bolstered by real world use cases
and data.

Specifically in relation to the networking API, it really is of somewhat
dubious value even if reporting everything correctly, as connectivity at
any given instant has no real bearing on connectivity status in the next
instant (the classic elevator example). It can be used for heuristics but
isn’t necessarily reliable in the mobile world.

Ken Wallis
Senior Product Manager - WebWorks

-----Original Message-----
From: Brian LeRoux <>
Reply-To: "" <>
Date: Wednesday, February 19, 2014 at 2:26 PM
To: "" <>
Subject: Re: w3c network information api shelved

>Josh I appreciate your perspective but getting more inputs and outputs
>Cordova and W3C is not a bad thing. Certainly there is a perception of how
>standards work.  would argue they haven't been working very well: big up
>front designs usually fail. Anyhow I welcome prototyping and discussion to
>make them, and us, better.
>On Wed, Feb 19, 2014 at 1:45 PM, Josh Soref <> wrote:
>> Shazron wrote:
>>  >
>>  >
>>  > our repo: 
>>  >
>> > Good thing we never updated itŠ
>> Based on the quirks in the documentation, it looks like the API is
>> useless.
>> ³you¹re on cellular (unspecified type)² on most of the platforms.
>> Everyone was demanding something more specific than that, and yet none
>> the OS vendors are offering it, and in reality nothing useful can be
>> w/ it.
>> Removing it is the right things.
>> On Wed, Feb 19, 2014 at 1:00 PM, Brian LeRoux <> wrote:
>> > I've been encouraging w3c members to bring these issue to us and to
>> >us
>> > work through implementation. The relationship so far has been more
>> >on
>> > us and that was probably not optimal for getting things done.
>> >we
>> > see them chime in.
>> Brian, that isn¹t how it works. To have a specification, you have to
>> real use cases, and real implementations, not toy use cases and not toy
>> implementations.
>> The forum for discussing standards is W3C. It¹s an open email list. It¹s
>> more responsive than the Cordova project (where pull requests often get
>> lost for months). And all feedback is tracked and will be addressed.
>> On 2/19/14, 4:05 PM, "Shazron" <> wrote:
>> > From that w3c thread, I came across this w3c github org:
>> >
>> >
>> > Seems they are gathering data on what's out there (including Cordova
>> >APIs).
>> Sure. If someone can come up with actual Use Cases, perhaps an API might
>> need to be created, but it¹s most likely the case that other APIs
>> exist (Video, Streaming, WebPerf) or will be created in those areas for
>> 80-90% of the real Use Cases, and in general specifications and software
>> should cover the 80-90%, not the 1%.

View raw message