MediaSourcePlayer implements IsTypeSupported().

media/base/android/media_codec_bridge.h

Index: media/base/android/media_codec_bridge.h
diff --git a/media/base/android/media_codec_bridge.h b/media/base/android/media_codec_bridge.h
index 3469b1804e7525fb423244162284c617169e7bee..2bbbd17a2b84a6d3a6940b2ca6b4f3753515a5f8 100644
--- a/media/base/android/media_codec_bridge.h
+++ b/media/base/android/media_codec_bridge.h
@@ -39,6 +39,9 @@ class MEDIA_EXPORT MediaCodecBridge {
   // Returns true if MediaCodec is available on the device.
   static bool IsAvailable();
 
+  // Returns if MediaCodecBridge can play |mime| type in |secure| mode.

[ddorwin, 2013/08/27 18:14:19]

1) Is |mime| the correct name?

2) Who is converting from web codec strings to Android-specific "mime types"? I
would think this would happen inside the bridge.

Assuming we address #2, #1 could be |codec| or something like that.

[xhwang, 2013/08/28 01:21:24]

Current code uses AudioCodecToMimeType and VideoCodecToMimeType to do the
translation.
https://code.google.com/p/chromium/codesearch#chromium/src/media/base/android...

What will the browser side have, a string for the codec, or a
media::AudioCodec/media::VideoCodec?
I am using char* and |mime| only to be consistent with the existing code :)

|mime| is really a bad name. But since Android API is using that all over the
place, I am not gonna fix it in this CL.

[ddorwin, 2013/08/28 02:28:50]

I think we should hide these platform-specific strings as deep as possible,
which would mean hiding it within the browser. I think the browser/renderer API
will use standard strings for all platforms. (Of course, this means doing more
work in the browser process, but I think it's the right thing to do from an API
perspective.)
Similarly, it would be nice to hide this inconsistency (use of "mime") in the
lowest levels. Do we use mime in the Android sense in the player, bridges, etc.
already? If not, I think it would be nice to present the normal use here. That
could be a different CL, though, since this CL seems to be getting close.

[xhwang, 2013/08/28 18:19:15]

I agree that we should not expose this non-standard mime to the outside world.
My question is what we should use instead? media::AudioCodec/media::VideoCodec,
or strings like "vp8", as listed in
https://code.google.com/p/chromium/codesearch#chromium/src/net/base/mime_util...
I guess string will be easier to pass here. I'll go with it and do conversion in
this file.
Agreed. Will do it in a separate CL, and probably after we have feature complete
since it's lower priority.

+  static bool CanPlayType(const char* mime, bool secure);

[ddorwin, 2013/08/27 18:14:19]

Why not use "const std::string&" ?

[xhwang, 2013/08/28 01:21:24]

Done.

+
   virtual ~MediaCodecBridge();
 
   // Resets both input and output, all indices previously returned in calls to