Blimp OAuth2 token retreival on application start up.

blimp/client/public/android/java/src/org/chromium/blimp_public/BlimpClientContext.java

Index: blimp/client/public/android/java/src/org/chromium/blimp_public/BlimpClientContext.java
diff --git a/blimp/client/public/android/java/src/org/chromium/blimp_public/BlimpClientContext.java b/blimp/client/public/android/java/src/org/chromium/blimp_public/BlimpClientContext.java
index f59b479619bd79dc38bbb744bcc170ad5bbcec58..6b7608e862919856aa905ffe3b7b5a8c9023a243 100644
--- a/blimp/client/public/android/java/src/org/chromium/blimp_public/BlimpClientContext.java
+++ b/blimp/client/public/android/java/src/org/chromium/blimp_public/BlimpClientContext.java
@@ -39,4 +39,15 @@ public interface BlimpClientContext {
      * Java Blimp code only.
      */
     void setDelegate(BlimpClientContextDelegate delegate);
+
+    /**
+     * Connect to Blimp engine.
+     * @param clientToken OAuth2 token.
+     */
+    void connect(String clientToken);

[David Trainor- moved to gerrit, 2016/08/05 15:49:09]

Should this be exposed in the public interface?  What do you think about making
the Authenticator hold a BlimpClientContextImpl (or some callback interface) and
calling something like onAuthTokenReceived() there?

[xingliu, 2016/08/05 17:17:00]

I think that's better, will discuss it with Tommy.

If we put get token function inside Blimp, then connect in the
BlimpClientContext interface is probably not needed.

If get token is put in chrome (in delegate), then connect in the interface is
needed.

[xingliu, 2016/08/09 04:17:45]

Done. Now token is handled in c++. No exposure in Java.

+
+    /**
+     * Get OAuth2 token for Blimp.
+     */
+    void getAuthToken();

[David Trainor- moved to gerrit, 2016/08/05 15:49:09]

Shouldn't the publicly exposed method just be connect()?  getAuthToken is an
implementation detail for how the BlimpClientContext actually sets up the
connection right?  wdyt?

[xingliu, 2016/08/05 17:17:00]

Oh, this function is probably badly named, what it does here is try to query the
token on application start up, for user who has already enable blimp and open
clank.

If we put get token function inside Blimp, some function for early start
up(maybe something like initialize() ) in BlimpClientContext interface is
probably needed.

If we can put get token function in chrome(in delegate), so external can
directly call and internal can call through the delegate, then this function in
BlimpClientContext interface is not needed. But connect() is needed.

[xingliu, 2016/08/09 04:17:45]

Removed.

 }