Confirmed users
141
edits
TPE RIL Network team/NetworkManagerEnhancement: Difference between revisions
Jump to navigation
Jump to search
m
TPE RIL Network team/NetworkManagerEnhancement (view source)
Revision as of 08:03, 16 July 2014
, 16 July 2014→2014/07/14
m (→2014/07/14) |
|||
| Line 14: | Line 14: | ||
=== 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. | * 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 | * 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. | ||
* 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. | ||
* 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. | ||