Descriptionmedia: Add MojoCdmServiceContext.
MojoCdmServiceContext will serve as a bridge between a MojoRendererService and a
MojoCdmService such that the renderer service can use the CDM service to decrypt
(and decode) encrypted contents.
With this change, now MojoCdmServiceContext owns and manages all MojoCdmService
instances so that MojoRendererService can find the correct CDM to use given a
|cdm_id|. As a result, MojoCdmService is not strongly bound to the pipe anymore.
An alternative to this is to have MojoCdmService still strongly bound to the
pipe, but notifies the MojoCdmServiceContext when the service is created and
destroyed. Here I was just following existing code like PermissionServiceContext
and GeolocationServiceContext.
TBR=sky@chromium.org
BUG=432998
Committed: https://crrev.com/ec48647eb0ed539e7436b3a299f8d5e5073c76f8
Cr-Commit-Position: refs/heads/master@{#334061}
Patch Set 1 #Patch Set 2 : address related comments in https://codereview.chromium.org/840473002/#ps160001 #
Total comments: 16
Patch Set 3 : rebase only #Patch Set 4 : comments addressed #
Total comments: 24
Patch Set 5 : comments addressed #
Total comments: 9
Patch Set 6 : rebase only #Patch Set 7 : comments addressed #
Messages
Total messages: 22 (3 generated)
|