[Remoting Mobile] Refactor TelemetryLogWriter to use centralized token getter
This CL refactors TelemetryLogWriter to use the centralized token getter from
ChromotingClientRuntime. This change gets rid of special handling logic for
authorizing the log writer.
Change-Id: I9ce3481408759b20546801b1f96294f7223b3076
BUG: 780736
Reviewed-on: https://chromium-review.googlesource.com/967520
Commit-Queue: Yuwei Huang <[email protected]>
Reviewed-by: Joe Downing <[email protected]>
Cr-Commit-Position: refs/heads/master@{#544861}diff --git a/remoting/client/jni/jni_oauth_token_getter.cc b/remoting/client/jni/jni_oauth_token_getter.cc
index 5cb29d7..abeaad3 100644
--- a/remoting/client/jni/jni_oauth_token_getter.cc
+++ b/remoting/client/jni/jni_oauth_token_getter.cc
@@ -44,8 +44,9 @@
delete callback;
}
-JniOAuthTokenGetter::JniOAuthTokenGetter() {
+JniOAuthTokenGetter::JniOAuthTokenGetter() : weak_factory_(this) {
DETACH_FROM_THREAD(thread_checker_);
+ weak_ptr_ = weak_factory_.GetWeakPtr();
}
JniOAuthTokenGetter::~JniOAuthTokenGetter() {
@@ -66,4 +67,8 @@
Java_JniOAuthTokenGetter_invalidateCache(env);
}
+base::WeakPtr<JniOAuthTokenGetter> JniOAuthTokenGetter::GetWeakPtr() {
+ return weak_ptr_;
+}
+
} // namespace remoting
