You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Venkata Kiran (JIRA)" <ji...@apache.org> on 2014/06/05 17:21:02 UTC

[jira] [Commented] (CB-3335) network.connection API should support "change" event

    [ https://issues.apache.org/jira/browse/CB-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018863#comment-14018863 ] 

Venkata Kiran commented on CB-3335:
-----------------------------------

This is an valuable feature to have. It is important to know what kind of connection does the device has. In our app, we had an option to allow users to select on which connectivity type they would allow the app to operate. They can select either Wifi or Mobile or both. I think this is an common use case with large number of other applications. In our case, we had to get the connectivity type and then check against the user selection, which how ever is not complex. But if Cordova can provide an option to notify on change of connectivity type, it will be easier for app developers.

> network.connection API should support "change" event
> ----------------------------------------------------
>
>                 Key: CB-3335
>                 URL: https://issues.apache.org/jira/browse/CB-3335
>             Project: Apache Cordova
>          Issue Type: Wish
>          Components: Plugin Network Information
>    Affects Versions: Master
>            Reporter: Mike Sierra
>            Priority: Minor
>              Labels: connection
>
> Based on doc, this feature spec'ed by W3C (http://bit.ly/YsZwEV) is missing from the network.connection API.  The "change" event should fire when there is a change in the type of available connection. These events are likely more important than online/offline with ubiquitous network connections available.  Use case: should my app sync data now, or cache and wait until in WiFi environment? (Caveat: event is poorly named, & overlaps "change" event that fires on form controls.)



--
This message was sent by Atlassian JIRA
(v6.2#6252)