The Mus window server can simply request a CompositorFrameSink for a root window, and it'll get a CompositorFrameSink implementaton with a cc::Display backing it as we do in jellyfish. The Mus window server really only needs to ship CompositorFrames with a single SurfaceDrawQuad and so it does not need a GpuChannelHost. We should refactor code to avoid using GpuChannelHost in Mus-WS.
Comment 1 by bugdroid1@chromium.org
, Nov 4 2016