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}
9 files changed
tree: c7c3049fccbfbfbc07a8e822749e79db41f570ca
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. fuchsia_webengine/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

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.