Move KeySystemInfo to media.

content/public/renderer/content_renderer_client.h

Index: content/public/renderer/content_renderer_client.h
diff --git a/content/public/renderer/content_renderer_client.h b/content/public/renderer/content_renderer_client.h
index 9de7a084bd50c5785570aa0cde7f7aa5ccb41859..daf8d4a650d7212d3725d12dc7160a71f17cc332 100644
--- a/content/public/renderer/content_renderer_client.h
+++ b/content/public/renderer/content_renderer_client.h
@@ -49,13 +49,16 @@ struct WebPluginParams;
 struct WebURLError;
 }
 
+namespace media {
+struct KeySystemInfo;
+}
+
 namespace content {
 class BrowserPluginDelegate;
 class DocumentState;
 class RenderFrame;
 class RenderView;
 class SynchronousCompositor;
-struct KeySystemInfo;
 struct WebPluginInfo;
 
 // Embedder API for participating in renderer logic.
@@ -243,7 +246,7 @@ class CONTENT_EXPORT ContentRendererClient {
 
   // Gives the embedder a chance to register the key system(s) it supports by
   // populating |key_systems|.
-  virtual void AddKeySystems(std::vector<KeySystemInfo>* key_systems);
+  virtual void AddKeySystems(std::vector<media::KeySystemInfo>* key_systems);

[xhwang, 2014/10/22 07:00:09]

jam: This is the tricky part of this CL. In ContentRendererClient, I am using an
struct in media. Is this allowed?

I am doing this because I need to move most part of
content/renderer/media/crypto/key_systems.* to media. So media code will also
need to access KeySystemInfo. An alternative is to keep both
content::KeySystemInfo and media::KeySystemInfo, then do the translation in
content/renderer/media code. But that seems unfortunate and will be hard to
maintain.

Please let me know what you think. Thanks!

[jam, 2014/10/23 20:12:22]

yep this is fine.

see other examples:
https://code.google.com/p/chromium/codesearch#search/&q=%22namespace%20media%...

 
   // Returns true if we should report a detailed message (including a stack
   // trace) for console [logs|errors|exceptions]. |source| is the WebKit-