Add configurable logic to decision to ignore duplicate init data #4572
Labels
priority: P3
Useful but not urgent
status: archived
Archived and locked; will not be updated
type: enhancement
New feature or request
Milestone
Have you read the FAQ and checked for duplicate open issues?
Yes
Is your feature request related to a problem? Please describe.
DrmEngine.newInitData()
decides whether to create a new session based on whether the initData has already been seen. We have some advanced DRM features which means sometimes we'd like to change this result to:Describe the solution you'd like
We'd like to provide a function in the DRM configuration which will return one of the three options listed above (something like 'FORCE_CREATE', 'FORCE_IGNORE', or 'CHECK_FOR_DUPLICATE')
Parameters for the above function will include the initData for the keySystem, and the keyStatuses:
Describe alternatives you've considered
I can't think of an alternative, but would welcome any suggestions
Additional context
The text was updated successfully, but these errors were encountered: