removed AndroidOverlayFactory

media/base/android_overlay_mojo_factory.h

Index: media/base/android_overlay_mojo_factory.h
diff --git a/media/base/android_overlay_mojo_factory.h b/media/base/android_overlay_mojo_factory.h
new file mode 100644
index 0000000000000000000000000000000000000000..04458bdd0a399dd2d85fea2fb7094819a0b78191
--- /dev/null
+++ b/media/base/android_overlay_mojo_factory.h
@@ -0,0 +1,20 @@
+// Copyright 2017 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 MEDIA_BASE_ANDROID_OVERLAY_MOJO_FACTORY_CB_H_
+#define MEDIA_BASE_ANDROID_OVERLAY_MOJO_FACTORY_CB_H_
+
+#include "base/callback.h"
+#include "base/macros.h"
+#include "media/base/android_overlay_config.h"
+
+namespace media {
+
+// Note that this compiles on non-android too.
+using AndroidOverlayMojoFactoryCB = base::RepeatingCallback<std::unique_ptr<
+    AndroidOverlay>(base::UnguessableToken&, const AndroidOverlayConfig&)>

[xhwang, 2017/06/01 05:50:59]

ISTM this file lives in media/base and this callback has nothing to do with
mojo. I wonder why we use "mojo" in the file/callback name? :)

[liberato (no reviews please), 2017/06/01 06:07:55]

good point.

the need for a base::UnguessableToken is specific to the mojo implementation of
the AO api.  it identifies the render frame that owns the overlay.  that's the
only connection.

i'm not sure if it could be moved under media/mojo, or if there's a build rule
that prevented it.  i'll give it a try.

+
+}  // namespace media
+
+#endif  // MEDIA_BASE_ANDROID_OVERLAY_MOJO_FACTORY_CB_H_