tree: 98d5a65e342c26d11ba84c123c7f9d9fcad05b91 [path history] [tgz]
  1. BUILD.gn
  2. configuration.h
  3. embedder.cc
  4. embedder.h
  5. embedder_internal.h
  6. embedder_unittest.cc
  7. entrypoints.cc
  8. entrypoints.h
  9. named_platform_channel_pair.h
  10. named_platform_channel_pair_win.cc
  11. named_platform_handle.h
  12. named_platform_handle_utils.h
  13. named_platform_handle_utils_posix.cc
  14. named_platform_handle_utils_win.cc
  15. pending_process_connection.cc
  16. pending_process_connection.h
  17. platform_channel_pair.cc
  18. platform_channel_pair.h
  19. platform_channel_pair_posix.cc
  20. platform_channel_pair_posix_unittest.cc
  21. platform_channel_pair_win.cc
  22. platform_channel_utils_posix.cc
  23. platform_channel_utils_posix.h
  24. platform_handle.cc
  25. platform_handle.h
  26. platform_handle_utils.h
  27. platform_handle_utils_posix.cc
  28. platform_handle_utils_win.cc
  29. platform_handle_vector.h
  30. platform_shared_buffer.cc
  31. platform_shared_buffer.h
  32. platform_shared_buffer_unittest.cc
  33. README.md
  34. scoped_ipc_support.cc
  35. scoped_ipc_support.h
  36. scoped_platform_handle.h
  37. test_embedder.cc
  38. test_embedder.h
mojo/edk/embedder/README.md

Mojo Embedder API

The Mojo Embedder API is an unstable, internal API to the Mojo system implementation. It should be used by code running on top of the system-level APIs to set up the Mojo environment (instead of directly instantiating things from src/mojo/edk/system).

Example uses: Service Manager, to set up the Mojo environment for Services; Chromium code, to set up the Mojo IPC system for use between processes. Note that most code should use the Mojo Public API (under src/mojo/public) instead. The Embedder API should only be used to initialize the environment, set up the initial MessagePipe between two processes, etc.