Headless: Support multiple TabSockets
TabSockets are intended to either be installed into the main world or
a isolated world created by Page.createIsolatedWorld. Previously we
only supported a single TabSocket per WebContents but that's unfortunate
with OOPIF. This patch lets us support multiple TabSockets up to one
per world per frame.
The mojoms have changed a bit with
TabSocket::AwaitNextMessageFromEmbedder moving to
HeadlessRenderFrameController::SendMessageToTabSocket which simplifies
recieveing a message from the embedder since a hanging IPC is no
longer needed.
Bug: 546953
Change-Id: I835ffcdf3bf9acd5be687074977346fb19f69d12
Reviewed-on: https://chromium-review.googlesource.com/543160
Commit-Queue: Alex Clarke <alexclarke@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#482990}24 files changed
