Consider breaking out some parts of networkingPrivate API into separate APIs under networking namespace.
As part of opening up networking API to kiosk apps, the API is being renamed to networking.onc.
The API contains some API methods that are not strictly related to ONC, and for which a better suited API name could be used. We should consider moving such methods into their own namespace. Additional benefit would be ability to control access to these APIs in more granular fashion.
Some possibilities:
networkingPrivate.startActivate
networkingPrivate.unlockCellularSim
networkingPrivate.setCellularSimState
- used to activate/set state of sim cards
- networking.cellular or networking.settings might be better namespaces
networkingPrivate.getCaptivePortalStatus
networkingPrivate.onPortalDetectionCompleted
- primary use case seems to be for Chrome OS automated testing, so networking.telemetry might be a suitable namespace (one that could be extended with other test methods)
networkingPrivate.verifyDestination
networkingPrivate.verifyAndEncryptCredentials
networkingPrivate.verifyAndEncryptData
- used primarily by Chromecast setup app to verify Chromecast certs
- networking.cast / networking.chromecast might be a good namespace
networkingPrivate.setWifiTDLSEnabledState
networkingPrivate.getWifiTDLSStatus
- used by cast extension - again maybe networking.cast/networking.chromecast, or networking.tdls, or networking.wifi
networkingPrivate.getDeviceStates
networkingPrivate.enableNetworkType
networkingPrivate.disableNetworkType
networkingPrivate.onDeviceStateListChanged
- maybe networking.device (as it primarily deals with networking devices)
- also, seems to be used primarily by settings, so networking.settings might be appropriate
Comment 1 by steve...@chromium.org
, Jan 5 2017