diff options
author | rockot <rockot@chromium.org> | 2016-01-29 15:09:49 -0800 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2016-01-29 23:10:41 +0000 |
commit | 51587279c85976821a3e9800dd8cc9082ffddf98 (patch) | |
tree | 942bb1cc03db6ae983a78533437515e1d8d29b59 /docs | |
parent | e4599ba549fdfab25669fc59b9c78b4a8fb2ce94 (diff) | |
download | chromium_src-51587279c85976821a3e9800dd8cc9082ffddf98.zip chromium_src-51587279c85976821a3e9800dd8cc9082ffddf98.tar.gz chromium_src-51587279c85976821a3e9800dd8cc9082ffddf98.tar.bz2 |
[mojo-doc] Add note about in-process messaging
BUG=None
TBR=satorux@chromium.org
Review URL: https://codereview.chromium.org/1647293003
Cr-Commit-Position: refs/heads/master@{#372451}
Diffstat (limited to 'docs')
-rw-r--r-- | docs/mojo_in_chromium.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/mojo_in_chromium.md b/docs/mojo_in_chromium.md index 58ab08e..9ec5588e 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 |