Mojo EDK: Avoid redundant queueing when sending to unknown peers

NodeController::SendPeerMessage queues outgoing messages if it
doesn't know the destination node, unless in the broker process where
this condition must mean the destination is no longer (or perhaps never
was) valid.

In the client process case, we almost always end up needing to request
an introduction from the broker in each SendPeerMessage call. This means
that in both the client and broker process cases, we almost always need
to attempt to acquire a handle to the broker NodeChannel anyway.

This CL does that and drops out early if we're in the broker process,
avoiding unnecessary queueing of undeliverable messages.

BUG=None

Review-Url: https://codereview.chromium.org/2784463004
Cr-Original-Commit-Position: refs/heads/master@{#460163}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 4e3eedb01d42a459acc405e87e7a0a72ca9c71b8
1 file changed
tree: 428b727916bfc5ed8144ec414c057ec5fa11b202
  1. android/
  2. common/
  3. edk/
  4. public/
  5. BUILD.gn
  6. DEPS
  7. OWNERS
  8. PRESUBMIT.py
  9. README.md
README.md

Mojo

Mojo is an IPC & binding mechanism for Chromium.

TODO(rockot): Describe the important subdirectories.