Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(224)

Unified Diff: docs/mojo_in_chromium.md

Issue 1647293003: [mojo-doc] Add note about in-process messaging (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 4 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: docs/mojo_in_chromium.md
diff --git a/docs/mojo_in_chromium.md b/docs/mojo_in_chromium.md
index 58ab08ea1d877275b790688f7c640cf1e77a490a..9ec5588e4376ea99f84b5d9562aa91348911e521 100644
--- a/docs/mojo_in_chromium.md
+++ b/docs/mojo_in_chromium.md
@@ -181,6 +181,11 @@ request and writes it to one end of the pipe. Eventually (and incidentally,
very soon after), `impl`'s internal `mojo::Binding` will decode this message and
dispatch a call to `impl.Frobinate()`.
+**NOTE:** In this example the service and client are in the same process, and
+this works just fine. If they were in different processes (see the example below
+in [Exposing Services in Chromium](#Exposing-Services-in-Chromium)), the call
+to `Frobinate()` would look exactly the same!
+
### Responding to Requests
A common idiom in Chromium IPC is to keep track of IPC requests with some kind
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698