TPE RIL Network team/NetworkManagerEnhancement: Difference between revisions

Line 38: Line 38:
* nsINetwokInterface connect()/disconnect() should return something like NS_OK, and then an async callback will be fired with the actual result.
* 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 async callback should be fired after the retry mechanism finishes running.
* If network interface fails to connect and a retry mechanism is ran, then the async callback should be fired after the retry mechanism finishes running.
** Sequence Diagram: http://goo.gl/SCR9G7
* 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.
* 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.
** Sequence Diagram: http://goo.gl/bn5Bbb
* 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.
* 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).
* '''Action''': wifi will tell us how wifi works (scan, associate, connect, disconnect, etc).
Confirmed users
258

edits