|author||Haoming Chen <firstname.lastname@example.org>||Sat Dec 01 01:01:14 2018|
|committer||John Rummell <email@example.com>||Mon Dec 03 19:00:24 2018|
Fix some EME spec links. Change-Id: I100098d1269c52a8378be33b3708311c3134cd18 Reviewed-on: https://chromium-review.googlesource.com/c/1357198 Reviewed-by: John Rummell <firstname.lastname@example.org> Reviewed-by: Xiaohan Wang <email@example.com>
This directory contains files that define the shared library interface between an Encrypted Media Extensions (EME) Content Decryption Module (CDM) and Chromium or other user agents. It is used to build both user agents and CDMs.
This is also referred to as the “CDM interface” in the context of library CDM and in this doc.
TODO(xhwang): Add more sections describing the CDM interface.
A new CDM interface that‘s still under development is subject to change. This is called an “experimental CDM interface”. To avoid compatibility issues, a user agent should not support an experimental CDM interface by default (it’s okay to support it behind a flag). Similarly, a CDM vendor should not ship a CDM using an experimental CDM interface to end users.
The experimental status of a CDM interface ends when the development is complete and the CDM interface is marked as stable. A stable CDM interface defines an application binary interface (ABI) between the CDM and the host, which should never be changed. Some minor ABI-compatible changes can still be made on a stable CDM interface to improve readability or to avoid unnecessary complexity. For example:
Note that even though these changes are ABI-compatible, the implementation may still need to be updated, e.g. to handle the new enum type in a switch case block.
On newer CDM interfaces, a static boolean member kIsStable is present to indicate whether the CDM interface is stable or experimental.