Initial commit of the blimp/ folder and target

blimp/client/android/blimp_jni_registrar.h

Index: blimp/client/android/blimp_jni_registrar.h
diff --git a/blimp/client/android/blimp_jni_registrar.h b/blimp/client/android/blimp_jni_registrar.h
new file mode 100644
index 0000000000000000000000000000000000000000..693d1bd303f31dd21f41e9cf829ed096c58036c1
--- /dev/null
+++ b/blimp/client/android/blimp_jni_registrar.h
@@ -0,0 +1,20 @@
+// Copyright 2015 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef BLIMP_CLIENT_ANDROID_BLIMP_JNI_REGISTRAR_H_
+#define BLIMP_CLIENT_ANDROID_BLIMP_JNI_REGISTRAR_H_
+
+#include <jni.h>
+
+namespace blimp {
+
+// Registers the native hooks for Java to native methods.  If this fails Java
+// objects won't be able to call native methods.  |env| is a JNI interface
+// pointer that holds all Java method signatures.  It's lifecycle is owned by
+// the native Java VM code.

[Wez, 2015/09/03 18:26:11]

I'd suggest:

"Registers native method hooks with the Java runtime specified by |env|. Returns
false if registration fails, in which case native methods are unavailable to
Java."

It wasn't clear to me reading the code whether the hooks actually retain
references to |env| or whether this method is self-contained?

[David Trainor- moved to gerrit, 2015/09/03 19:06:00]

Ah yeah it's self contained (at least as far as our automatically generated JNI
code is concerned).

+bool RegisterBlimpJni(JNIEnv* env);
+
+}  // namespace blimp
+
+#endif  // BLIMP_CLIENT_ANDROID_BLIMP_JNI_REGISTRAR_H_