Home | History | Annotate | only in /external/chromium_org/mojo/embedder
Up to higher level directory
NameDateSize
channel_init.cc03-Dec-20141.8K
channel_init.h03-Dec-20141.6K
DEPS03-Dec-2014257
embedder.cc03-Dec-20146.1K
embedder.h03-Dec-20143.6K
embedder_unittest.cc03-Dec-201419.8K
platform_channel_pair.cc03-Dec-2014796
platform_channel_pair.h03-Dec-20143.6K
platform_channel_pair_posix.cc03-Dec-20144.1K
platform_channel_pair_posix_unittest.cc03-Dec-20148.5K
platform_channel_pair_win.cc03-Dec-20144.1K
platform_channel_utils_posix.cc03-Dec-20146.2K
platform_channel_utils_posix.h03-Dec-20143.5K
platform_handle.cc03-Dec-2014856
platform_handle.h03-Dec-20141.1K
platform_handle_utils.h03-Dec-20141.1K
platform_handle_utils_posix.cc03-Dec-2014659
platform_handle_utils_win.cc03-Dec-2014906
platform_handle_vector.h03-Dec-20141.1K
README.md03-Dec-2014641
scoped_platform_handle.h03-Dec-20141.6K
test_embedder.cc03-Dec-20141.3K
test_embedder.h03-Dec-2014834

README.md

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