• Home
  • History
  • Annotate
  • only in /external/chromium_org/mojo/embedder/
NameDateSize

..05-Nov-201412 KiB

channel_init.cc05-Nov-20141.8 KiB

channel_init.h05-Nov-20141.6 KiB

DEPS05-Nov-2014257

embedder.cc05-Nov-20146.1 KiB

embedder.h05-Nov-20143.6 KiB

embedder_unittest.cc05-Nov-201419.8 KiB

platform_channel_pair.cc05-Nov-2014796

platform_channel_pair.h05-Nov-20143.6 KiB

platform_channel_pair_posix.cc05-Nov-20144.1 KiB

platform_channel_pair_posix_unittest.cc05-Nov-20148.5 KiB

platform_channel_pair_win.cc05-Nov-20144.1 KiB

platform_channel_utils_posix.cc05-Nov-20146.2 KiB

platform_channel_utils_posix.h05-Nov-20143.5 KiB

platform_handle.cc05-Nov-2014856

platform_handle.h05-Nov-20141.1 KiB

platform_handle_utils.h05-Nov-20141.1 KiB

platform_handle_utils_posix.cc05-Nov-2014659

platform_handle_utils_win.cc05-Nov-2014906

platform_handle_vector.h05-Nov-20141.1 KiB

README.md05-Nov-2014641

scoped_platform_handle.h05-Nov-20141.6 KiB

test_embedder.cc05-Nov-20141.3 KiB

test_embedder.h05-Nov-2014834

README.md

1Mojo Embedder API
2=================
3
4The Mojo Embedder API is an unstable, internal API to the Mojo system
5implementation. It should be used by code running on top of the system-level
6APIs to set up the Mojo environment (instead of directly instantiating things
7from src/mojo/system).
8
9Example uses: Mojo shell, to set up the Mojo environment for Mojo apps; Chromium
10code, to set up the Mojo IPC system for use between processes. Note that most
11code should use the Mojo Public API (under src/mojo/public) instead. The
12Embedder API should only be used to initialize the environment, set up the
13initial MessagePipe between two processes, etc.
14