Lines Matching +full:api +full:- +full:level

10 [**JavaScript**](#JavaScript-Bindings), or [**Java**](#Java-Bindings)) as well
15 the top-level [Services documentation](/services/README.md).
22 Mojo is a collection of runtime libraries providing a platform-agnostic
25 convenient message passing across arbitrary inter- and intra-process boundaries.
30 … support APIs in the middle](https://docs.google.com/drawings/d/1RwhzKblXUZw-zhy_KDVobAYprYSqxZzop…
33 In order to use any of the more interesting high-level support libraries like
35 This is a one-time initialization which remains active for the remainder of the
37 API, or through a dynamically linked library.
43 [**Mojo Core Embedder API**](/mojo/core/embedder/README.md) for more details.
51 dynamically-linked Mojo Core library (`libmojo_core.so` or `mojo_core.dll`)
57   - The working directory of the application
58   - A directory named by the `MOJO_CORE_LIBRARY_PATH` environment variable
59   - A directory named explicitly by the application at runtime
62 dynamic Mojo Core instead calls `MojoInitialize()` from the C System API. This
64 subsequent Mojo API usage within the process.
66 Note that the Mojo Core shared library presents a stable, forward-compatible C
67 ABI which can support all current and future versions of the higher-level,
68 public (and not binary-stable) System and Bindings APIs.
70 ## C System API
72 [**C System API**](/mojo/public/c/system/README.md) is usable on any thread for
73 the remainder of the process's lifetime. This is a lightweight API with a
74 relatively small, stable, forward-compatible ABI, comprising the total public
75 API surface of the Mojo Core library.
77 This API is rarely used directly, but it is the foundation upon which all
78 higher-level Mojo APIs are built. It exposes the fundamental capabilities to
83 ## Platform Support API
84 Mojo provides a small collection of abstractions around platform-specific IPC
86 [Platform API](/mojo/public/cpp/platform/README.md) documentation for details.
88 ## High-Level System APIs
89 There is a relatively small, higher-level system API for each supported
90 language, built upon the low-level C API. Like the C API, direct usage of these
95 The [**C++ System API**](/mojo/public/cpp/system/README.md) provides a layer of
96 C++ helper classes and functions to make safe System API usage easier:
97 strongly-typed handle scopers, synchronous waiting operations, system handle
102 The [**JavaScript System API**](/third_party/blink/renderer/core/mojo/README.md)
104 low-level C API.
107 The [**Java System API**](/mojo/public/java/system/README.md) provides helper
109 the low-level C API.
111 ## High-Level Bindings APIs
114 an idiomatic method-calling interface in the target language of choice. This is
123 simplifying the code -- and ultimately hiding the message pipe -- on either side
127 By far the most commonly used API defined by Mojo, the
128 [**C++ Bindings API**](/mojo/public/cpp/bindings/README.md) exposes a robust set
131 nested sync IPC, versioning, bad-message reporting, arbitrary message filter
135 The [**JavaScript Bindings API**](/mojo/public/js/README.md) provides helper
139 The [**Java Bindings API**](/mojo/public/java/bindings/README.md) provides
146 deal-breaker is that a useful IPC mechanism must support transfer of native
148 non-new IPC things that do support this capability (*e.g.* D-Bus) have their own
163 ### Can I use in-process message pipes?
165 crosses a process boundary -- in fact this detail is intentionally obscured.
172 `PostTask` to the `Binding`'s `TaskRunner` with the added -- but often small --
179 [`chromium-mojo@chromium.org`](https://groups.google.com/a/chromium.org/forum/#!forum/chromium-mojo…