OSDN Git Service

Stop supporting legacy ConnectivityManager routing methods in M.
authorLorenzo Colitti <lorenzo@google.com>
Wed, 29 Jul 2015 02:41:21 +0000 (11:41 +0900)
committerLorenzo Colitti <lorenzo@google.com>
Fri, 31 Jul 2015 02:08:27 +0000 (11:08 +0900)
commitffc42b0b7be29ee4118e0515d5ab024927bcb8ca
tree2101af35baee3797ce8542187ff87114f1265c72
parent5db4cc8fee8b919b5f62f222af92a4e995ca6a70
Stop supporting legacy ConnectivityManager routing methods in M.

The methods startUsingNetworkFeature, stopUsingNetworkFeature and
requestRouteToHost were @removed in all the M preview builds, but
internal and external developers have noted that this imposes
additional burden for applications that need to work across
multiple platform versions because it causes compile-time errors.

We switched from @removed back to @deprecated to avoid these
problems. In order to effectively deprecate these methods, which
are error-prone and insecure, make them throw
UnsupportedOperationException if the app's target SDK is M or
above.

Because there are still one or two places in system code that use
these APIs, exempt Process.SYSTEM_UID and the OMA-DM client from
the check for now.

Bug: 22728205
Change-Id: I790bd32f3aa8067cbb625962a209bb9232f4b58c
core/java/android/app/SystemServiceRegistry.java
core/java/android/net/ConnectivityManager.java
services/tests/servicestests/src/com/android/server/ConnectivityServiceTest.java