tree: d245b091e585f2b1693eb8805e2431804d2ceb24 [path history] [tgz]
  1. channel_init.cc
  2. channel_init.h
  3. DEPS
  4. embedder.cc
  5. embedder.h
  6. embedder_unittest.cc
  7. platform_channel_pair.cc
  8. platform_channel_pair.h
  9. platform_channel_pair_posix.cc
  10. platform_channel_pair_posix_unittest.cc
  11. platform_channel_pair_win.cc
  12. platform_channel_utils_posix.cc
  13. platform_channel_utils_posix.h
  14. platform_handle.cc
  15. platform_handle.h
  16. platform_handle_utils.h
  17. platform_handle_utils_posix.cc
  18. platform_handle_utils_win.cc
  19. platform_handle_vector.h
  20. platform_shared_buffer.h
  21. platform_support.h
  22. PRESUBMIT.py
  23. README.md
  24. scoped_platform_handle.h
  25. simple_platform_shared_buffer.cc
  26. simple_platform_shared_buffer.h
  27. simple_platform_shared_buffer_posix.cc
  28. simple_platform_shared_buffer_unittest.cc
  29. simple_platform_shared_buffer_win.cc
  30. simple_platform_support.cc
  31. simple_platform_support.h
  32. test_embedder.cc
  33. test_embedder.h
mojo/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/system).

Example uses: Mojo shell, to set up the Mojo environment for Mojo apps; 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.