With FrameSinkIdAllocator on its way to landing soon (see https://codereview.chromium.org/2691363002/), "SurfaceIdAllocator" is a bit of a misnomer. It's really a LocalSurfaceIdAllocator as it doesn't touch (or care about) the FrameSinkId. I think we should rename SurfaceIdAllocator to LocalSurfaceIdAllocator for consistency.
In the future, when SurfaceIds are allocated in the parent, the parent will actually have a LocalSurfaceIdAllocator as the FrameSinkId for the child remains fixed.
Comment 1 by ericrk@chromium.org
, Feb 22 2017