Populate canPlayType to renderer

chrome/common/encrypted_media_messages_android.h

Index: chrome/common/encrypted_media_messages_android.h
diff --git a/chrome/common/encrypted_media_messages_android.h b/chrome/common/encrypted_media_messages_android.h
new file mode 100644
index 0000000000000000000000000000000000000000..e9141a1f76ca1a5165db825de27ec8427a3ef784
--- /dev/null
+++ b/chrome/common/encrypted_media_messages_android.h
@@ -0,0 +1,37 @@
+// Copyright 2013 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.
+
+// IPC messages for EME on android.
+// Multiply-included message file, hence no include guard.
+
+#include <string>
+#include <vector>
+
+#include "ipc/ipc_message_macros.h"
+
+#define IPC_MESSAGE_START EncryptedMediaMsgStart
+
+IPC_STRUCT_BEGIN(SupportedKeySystem)
+  // Key system UUID.
+  IPC_STRUCT_MEMBER(std::vector<uint8>, uuid)
+
+  // Name of the key system.

[ddorwin, 2013/09/16 17:58:10]

I don't think the Android IPC layer needs to know about key system strings or
parents. We probably do want to have some way to pass attribute(s) of the uuid
so we can add subdomains.

[xhwang, 2013/09/17 18:56:46]

Yeah, we probably only care about UUID, container type and codecs here.
KeySystemInfo et al will do the UUID -> key_system translation.

[qinmin, 2013/09/17 19:21:06]

Done.

+  IPC_STRUCT_MEMBER(std::string, key_system)
+
+  // Name of the parent key system.
+  IPC_STRUCT_MEMBER(std::string, parent_key_system)
+
+  // A list of supported codecs.
+  IPC_STRUCT_MEMBER(std::vector<std::string>, codecs)
+
+  // Whether video composition is enabled.
+  // TODO(qinmin): this may be replaced by a new key_system string.
+  IPC_STRUCT_MEMBER(bool, video_composition_enabled)

[xhwang, 2013/09/17 18:56:46]

Also add container type here? For now, we only support MP4.

[xhwang, 2013/09/17 18:56:46]

Can we have:

IPC_STRUCT_MEMBER(std::vector<std::string>, compositing_codecs)

and

IPC_STRUCT_MEMBER(std::vector<std::string>, non_compositing_codecs)

Then we can probably drop |video_composition_enabled|.

[qinmin, 2013/09/17 21:26:23]

passing the codecs bitmask inside the IPC
On 2013/09/17 18:56:46, xhwang wrote:

[qinmin, 2013/09/17 21:26:23]

Done.

+IPC_STRUCT_END()
+
+// Messages sent from the renderer to the browser.
+
+// Synchronously get a list of supported EME key systems.
+IPC_SYNC_MESSAGE_ROUTED0_1(ChromeViewHostMsg_GetSupportedKeySystems,
+                           std::vector<SupportedKeySystem>)

[xhwang, 2013/09/17 18:56:46]

It seems the UUID, container types and codecs are orthogonal to each other. If
we have two lists of codecs as suggested above (compositing_codecs and
non_compositing_codecs). Then we don't need the std::vector here. Only one
SupportedKeySystem will have all information we need.

[qinmin, 2013/09/17 21:26:23]

Done.