Remove support for custom DASH ContentProtection schemas

[joeyparrish]

Since almost the beginning of Shaka Player, we have supported the parsing of a DASH <ContentProtection> element with a non-standard schema. Today this is done through a callback configured via manifest.dash.customScheme.

But does anyone still use this? In 2014, we had been provided test content where this callback was necessary to get the license server URL. However, I expect the industry at large has moved to more standard DASH manifests, and removing this may allow us to simplify some things in our manifest structure and in DrmEngine.

So please reply if:

• You would object to our removing the manifest.dash.customScheme option
• You used to use customScheme, but don't any more
• You have custom manifest parsers that output license servers or other features in DrmInfo beyond keySystem, initData, or keyIds
• You have other thoughts to share on this topic

Thanks!

[joeyparrish]

Since there has been no feedback in 9 weeks, I'll take that as consent to remove manifest.dash.customScheme from Shaka Player in v2.6.

Thanks!