The name DisplayCompositor isn't a great name for what the code does. It handles creating MojoCompositorFrameSinks, creating cc::Displays, managing FrameSink hierarchies and informing DisplayCompositorClient about new Surfaces.
DisplayCompositor isn't cc::Display, which is the "display compositor", and it doesn't composite things. So a new name is in order.
The public API for DisplayCompositor is similar to what cc::FrameSinkManager offers except over Mojo. DisplayCompositor also handles some cc::SurfaceManager functionality.
I would say call it FrameSinkManager but that conflicts with the existing cc::FrameSinkManager. Another option would be GpuFrameSinkManager, similar to GpuCompositorFrameSink, but we've also concluded that the new service shouldn't be called GPU because it's confusing.
Comment 1 by danakj@chromium.org
, Mar 28 2017