OSDN Git Service

ConnectivityMetricsLogger: Switch to "pull" model
authorPavel Zhamaitsiak <pavelz@google.com>
Fri, 1 Apr 2016 01:43:14 +0000 (18:43 -0700)
committerPavel Zhamaitsiak <pavelz@google.com>
Fri, 1 Apr 2016 01:43:14 +0000 (18:43 -0700)
commitd1cb256b3efd2c00f1c44541b5589c2ea17b3cb8
tree43c4cfe442adb2c623bf19508b7051faa7f1710d
parent3d09db6f7a181b26e2541b90b379d68ab0f8ed32
ConnectivityMetricsLogger: Switch to "pull" model

If subscriber is in external app, its process can be killed. This would
lead to loss of events. To avoid that, we will be storing events in the
logger service. Clients can periodically pull data from it.

Another option for client apps is to register PendingIntent which will be
sent when certain number of new events has been received.

If events are logged at unexpectedly high rate from particular component,
then throttling mechanism will activate and new events will be blocked for
some time from that component.

Change-Id: I710409626eb5a42bcd3fe8126eac6b756fa1ab8b
Android.mk
core/java/android/net/ConnectivityMetricsEvent.aidl
core/java/android/net/ConnectivityMetricsEvent.java
core/java/android/net/ConnectivityMetricsLogger.java
core/java/android/net/IConnectivityMetricsLogger.aidl
core/java/android/net/IConnectivityMetricsLoggerSubscriber.aidl [deleted file]
services/core/java/com/android/server/connectivity/MetricsLoggerService.java