1Mojo Public API 2=============== 3 4The Mojo Public API is a binary stable API to the Mojo system. There are 5several components to the API: 6 7Bindings 8-------- 9 10This directory contains a static library that clients can link into their 11binary. The contents of this directory are not binary stable because each 12client is free to use whichever version they prefer. 13 14This directory also contains a compiler that translates mojom interface 15definition files into idiomatic bindings for various languages, including 16C++ and JavaScript. Clients are expected to statically link with the generated 17code, which reads and writes the binary stable IPC message format. 18 19GLES2 20----- 21 22The IPC protocol used to communicate between Mojo client and the GLES2 23service is not binary stable. To insulate themselves from changes in this 24protocol, clients are expected to link dynamically against the standard GLES2 25headers from Khronos and the headers in this directory, which provide an 26adaptor between the GLES2 C API and the underlying IPC protocol. 27 28System 29------ 30 31This directory defines the interface between Mojo clients and the Mojo IPC 32system. Although the Mojo IPC message format is binary stable, the mechanism 33by which these messages are transported is not stable. To insulate themselves 34from changes in the underlying transport, clients are expected to link against 35these headers dynamically. 36 37Tests 38----- 39 40This directory contains tests for code contained in the public API. Mojo 41clients are expected to ignore this directory. 42