commit | c37e147b6f5db73af4d2bc3a496f2573ff6e9f79 | [log] [tgz] |
---|---|---|
author | Giovanni Ortuño Urquidi <ortuno@chromium.org> | Fri May 20 02:41:54 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 20 02:41:54 2022 |
tree | c7c3049fccbfbfbc07a8e822749e79db41f570ca | |
parent | 6cda78790371d5639e737471bb820dccf7f04cd1 [diff] |
system-extensions: Introduce InterfaceProvider and set up its connection This is CL #2 in the chain based on the following design doc: https://docs.google.com/document/d/1a7ncICMSFfvzXTKeOZ3WkzR7dVI6uI6sz7SPaf4_7W8/edit# This CL: * (browser-side) Adds a InterfaceProvider instance to ServiceWorkerHost * (browser-side) When starting a service worker, we create both remote and receiver endpoints for InterfaceProvider. We then pass the remote endpoint to ServiceWorkerHost as part of CompleteStartWorkerPreparation and we send the receiver endpoint to the renderer as part of EmbeddedWorkerStartParams. * (renderer-side) We save the receiver endpoint of InterfaceProvider and bind it on the worker thread in WorkerContextStarted. * (rendere-side) have ServiceWorkerContextClient implement InterfaceProvider. CL Chain: [1] Adds a BinderRegistry and registers a Blink Extensions interface (https://crrev.com/c/3622154) [2] Introduce InterfaceProvider and set up its connection (This CL) [3] Add StartWorkerWithEndpointForScope and use it in system extensions (https://crrev.com/c/3641084) Bug: b/221124268 Change-Id: Ia3e433827e904d649372ced26beacafadb97dd29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3640749 Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Ken Rockot <rockot@google.com> Commit-Queue: Giovanni Ortuno Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/heads/main@{#1005593}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.