Mojo: Support lazy serialization.

Implements two new public C API calls: MojoCreateMessage and
MojoGetMessageContext. This constitutes the bulk of what's needed to
support basic lazy message serialization as described in the proposal[1].

Follow-up CLs will introduce additional API surface - namely
MojoSerializeMessage and MojoGetSerializedMessageContents -- and
rename or rework existing APIs to match the details of the proposal.

[1] https://groups.google.com/a/chromium.org/forum/#!topic/chromium-mojo/4CA0Ip56lgA

BUG=725321

Change-Id: Ifdd0ee9ed69ab49c6324ea3f02e1efab74ea5175
Reviewed-on: https://chromium-review.googlesource.com/527556
Commit-Queue: Ken Rockot <rockot@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#478791}

CrOS-Libchrome-Original-Commit: 15b2b0b0e96b31574fd1a975a9acef92a71a7842
19 files changed
tree: 6d281efbc3d27008b59c2b5a7fdb08f4839d6ab2
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/