Status: Started Owner: [email protected] Labels: Type-Cleanup Pri-2 OS-All Area-BrowserBackend Size-Medium Mstone-3 Video
New issue 17107 by [email protected]: Clean up PipelineImpl, PipelineThread and FilterHostImpl mess http://code.google.com/p/chromium/issues/detail?id=17107 There's no reason why these classes should be separated. PipelineThread and FilterHostImpl should be merged into PipelineImpl, and we can add ref-counting to the Pipeline interface so we can post messages without relying on yet another proxy class. FilterHostImpl itself is quite useless in it's present form, and the only benefit it provides is that it remembers the FilterType constant. However an std::map<FilterType, MediaFilter*> would accomplish the same thing. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
