TPE RIL Network team/NetworkManagerEnhancement: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 13: Line 13:
== Discussion ==
== Discussion ==
=== 2014/07/14 ===
=== 2014/07/14 ===
* nsINetwokInterface connect()/disconnect() should return something like NS_OK, and then an async callback will be fired with the actual result.
* If network interface fails to connect and a retry mechanism is ran, then the asnync callback should be fired after the retry mechanism finishes running.
* Network interfaces are not supposed to connect themselves automatically. If there is any status change, e.g. radio on or data registered, these should be reported to NetworkManager and let NetworkManager decide whether to connect() or not.
* The problem for wifi is that when APs are available after a while, wpa_supplicant will connect to the AP automatically. But with this new architecture, it should wait for connect() to be called by NetworkManager.
* '''Action''': wifi will tell us how wifi works (scan, associate, connect, disconnect, etc).


= Routing improvements =
= Routing improvements =

Revision as of 08:01, 16 July 2014

meta bug

Internal interface changes

Proposal

Bugs

  • bug 990458 - B2G RIL: replace the use of 'network-interface-state-changed' events with updateNetworkInterface() API.
  • bug 904542 - B2G NetworkManager: Redefine the nsINetworkInterface
  • bug 911713 - B2G NetworkManager: Move policy control logic to NetworkManager
  • bug 928861 - B2G NetworkManager: Provide a more generic function for connecting
  • No bug yet - exponse only ‘NetworkInfo’ in NetworkManager

Discussion

2014/07/14

  • nsINetwokInterface connect()/disconnect() should return something like NS_OK, and then an async callback will be fired with the actual result.
  • If network interface fails to connect and a retry mechanism is ran, then the asnync callback should be fired after the retry mechanism finishes running.
  • Network interfaces are not supposed to connect themselves automatically. If there is any status change, e.g. radio on or data registered, these should be reported to NetworkManager and let NetworkManager decide whether to connect() or not.
  • The problem for wifi is that when APs are available after a while, wpa_supplicant will connect to the AP automatically. But with this new architecture, it should wait for connect() to be called by NetworkManager.
  • Action: wifi will tell us how wifi works (scan, associate, connect, disconnect, etc).

Routing improvements

Bugs

  • bug 997654 - B2G RIL: let each network handle its own host routes
  • bug 973543 - B2G RIL: host routes removed unexpectedly when data call is shared
  • No bug yet - B2G RIL: add callbacks in routing requests in NetworkService

Discussion

None

Other improvements

Bugs

  • No bug yet - Move tethering code out of NetworkManager

Discussion

None

Web API changes

Proposal

Use case

Bugs

  • bug 922584 - B2G RIL: provide WebAPI to setup network connections and expose connection state

Discussion

https://taiwan.etherpad.mozilla.org/1002

Retrieved from "https://wiki.mozilla.org/index.php?title=TPE_RIL_Network_team/NetworkManagerEnhancement&oldid=997294"