File: README.md

package info (click to toggle)
chromium 139.0.7258.127-1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 6,122,068 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (16 lines) | stat: -rw-r--r-- 851 bytes parent folder | download | duplicates (6) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
 
# README

This folder contains code to support W3C Encrypted Media Extensions (EME),
key systems and Content Decryption Modules (CDM). It's under `//components`
folder so they can be shared by multiple embedders of content, e.g. `//chrome`
and `//android_webview`. See
[`//components` use cases](https://source.chromium.org/chromium/chromium/src/+/main:components/README.md#use-cases)
for more context.

This means that only content embedders can depend on targets in this folder,
including `//chrome`, `//chromecast`, `//android_webview`, `//fuchsia_web`, and
`//content/shell` (test content embedder). Other folders, especially `//media`
and `//content`, should NOT depend on targets in this folder.

In general, key system specific logic should not be in `//media` or `//content`.
So it's also a good practice to put them under `//components/cdm`.