[chromecast] Let MediaPipelineBackendManager track media resources |
||||
Issue descriptionNow that we have a central place to manage pipeline backends in MediaPipelineBackendManager, it could internally track media resources instead of passing MediaResourceTracker around. This would be more correct (because it will be hard to forget calling MediaResourceTracker functions) and much cleaner. As part of this refactor, we might also be able to get rid of MediaPipelineClient::pipeline_backend_created_cb and MediaPipelineClient::pipeline_backend_destroyed_cb.
,
Jul 13 2016
,
Jul 14 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 31 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by alokp@chromium.org
, Mar 29 2016