UserMediaClientImpl currently takes care of serializing and processing getUserMedia requests.
ApplyConstraints requests need to be serialized together with getUserMedia requests, which will make UserMediaClientImpl even more complex than it is now.
The proposal is to move getUserMedia processing out of UMCI into a UserMediaProcessor and let UMCI handle serialization of getUserMedia and applyConstraints request, leaving processing to separate classes for easier maintenance.
UMCI also takes care of device enumeration requests, but refactoring in that area is outside the scope of this bug.
Comment 1 by bugdroid1@chromium.org
, Sep 14 2017