tree: a22f5fc9cd8e3e58df0a385882b7f7c2639dc0b0 [path history] [tgz]
  1. BUILD.gn
  2. DEPS
  3. README.md
  4. chromium_service.cc
  5. chromium_service.h
  6. crash_reporter_builtin.cc
  7. crash_reporter_client.h
  8. crash_reporter_system.cc
  9. external_connector.h
  10. external_connector_impl.cc
  11. external_connector_impl.h
  12. external_service.cc
  13. external_service.h
  14. process_setup.cc
  15. process_setup.h
  16. service_process.h
  17. standalone_mojo_broker.cc
  18. standalone_service_main.cc
  19. tracing_client.h
  20. tracing_client_dummy.cc
  21. tracing_client_dummy.h
  22. tracing_client_impl.cc
  23. tracing_client_impl.h
chromecast/external_mojo/external_service_support/README.md

External Mojo service support

This directory contains utilities to ease development of Mojo services that run in processes outside of Chromium/cast_shell. The simplest model is to create a subclass of ‘ServiceProcess’ (and implement ‘ServiceProcess::Create()’ that returns an instance of that subclass), and link with ‘standalone_service_main’ to create the executable. In your ‘ServiceProcess’ implementation, you can bind to Mojo interfaces using the provided ‘Connector’ pointer, and/or register your own Mojo services for use by other processes.

The ‘ChromiumServiceWrapper’ class is intended to allow Mojo services that were intended to be embedded into cast_shell (or other ServiceManager embedder) to be moved into a completely separate process. It forwards ‘BindInterface()’ calls to the ‘service_manager::Service’ API. You can use ‘CreateChromiumServiceReceiver()’ to create a ‘mojo::PendingReceiver<service_manager::Service>’ to emulate the normal service creation flow; the ‘service_manager::Service::OnStart()’ method will be called automatically.

The ‘standalone_mojo_broker’ is intended for use on platforms where there is no cast_shell running; this allows Mojo services outside of cast_shell to communicate with each other without any Chromium embedder on the system.