GitLab

Registering a FrameSinkId delimits the beginning of the lifetime of a
FrameSinkId. From Viz's perspective that ID is valid until
InvalidateFrameSinkId is called. RegisterFrameSinkId also bundles
a HostFrameSinkClient (was FrameSinkObserver) that listens for new surfaces
submitted to the registered FrameSinkId.

This CL allows us to replace multiple call sites to RegisterFrameSink /
InvalidateFrameSinkId in content that go directly to FrameSinkManagerImpl
with calls to HostFrameSinkManager, taking us closer to a point where
content does not directly use FrameSinkManagerImpl.

This CL is also a prerequisite for using HostFrameSinkManager in the
window server because it introduces a mechanism for listening for events
pertaining to a particular FrameSinkId which is a requirement for the
window server. This interface will be used for events as well in the
future.

Bug: 657959
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation
Change-Id: I3e1343ea6cfbe6b3d39ba2fcd23d193dd2c3e4a0
Reviewed-on: https://chromium-review.googlesource.com/595147Reviewed-by: Bo Liu <boliu@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Ria Jiang <riajiang@chromium.org>
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491386}