Add cdm::ContentDecryptionModule_9

content_decryption_module_broker.h

+// Copyright 2016 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 CDM_CONTENT_DECRYPTION_MODULE_BROKER_H_
+#define CDM_CONTENT_DECRYPTION_MODULE_BROKER_H_
+
+#if defined(_MSC_VER)
+typedef unsigned char uint8_t;
+typedef unsigned int uint32_t;
+#else
+#include <stdint.h>
+#endif
+
+#include "media/cdm/api/content_decryption_module_export.h"
+
+extern "C" {
+// Returns the |response| to ProcessHostChallenge(). If the challenge fails,
+// |response| = nullptr and |response_size| = 0. |user_data| must be the value
+// passed in to ProcessHostChallenge().
+typedef void (*HostResponseCallback)(const uint8_t* response,

[xhwang, 2016/10/28 18:18:14]

I am prototyping this and found "Callback" to be misleading, in the code it'll
look like:

response_callback(response, size, user_data);

Maybe this should be "response_func"?

[jrummell, 2016/10/31 21:04:37]

Done.

+                                     uint32_t response_size,
+                                     void* user_data);

[tinskip, 2016/10/27 00:32:47]

s/user_data/context/ here and below?  A bit clearer as "user_data" can be
construed as, well, user data.

[jrummell, 2016/10/31 21:04:37]

Done.

+
+// This method receives the |challenge| from the CDM as well as a list of
+// additional binary file paths created by the host and a callback function.
+// |response_callback| is called when the challenge has been processed, passing
+// |user_data| along with the desired response data.
+CDM_API void ProcessHostChallenge(const uint8_t* challenge,
+                                  uint32_t challenge_size,
+                                  const char** binary_file_paths,

[xhwang, 2016/10/28 06:34:25]

In chromium the chat type for base::FilePath is char on Posix and wchar_t on
Windows:

https://cs.chromium.org/chromium/src/base/files/file_path.h?rcl=0&l=12

So passing char** here seems problematic on Windows.

[jrummell, 2016/10/31 21:04:37]

Done.

+                                  uint32_t num_binary_file_paths,
+                                  HostResponseCallback response_callback,

[xhwang, 2016/10/28 06:34:25]

Can we require this callback to be called synchronously? Otherwise, it's tricky
to make sure |user_data|'s lifetime.

[xhwang, 2016/10/28 06:53:58]

Actually, if we require this callback to be called synchronously, does it make
sense to just provide two output parameters?

Is there a upper limit of the size of the response? If so, we can pre-allocate
memory for the response and let the CDM broker to fill the response in. 

+                                  void* user_data);
+}
+
+#endif  // CDM_CONTENT_DECRYPTION_MODULE_BROKER_H_