Bug 1040080 - Update nsIMessageManager.idl notes about in-process child process message manager. r=smaug
authorJim Mathies <jmathies@mozilla.com>
Tue, 22 Jul 2014 08:56:59 -0500
changeset 195529 d62df3aa085bf9259143c7b873d4ee179b2a7f88
parent 195528 e945647d29337bcf9d15dce6326886018607eca9
child 195530 8a4691f767ea2c85302ffd65c5b5230ab6521d85
push id27185
push userkwierso@gmail.com
push dateWed, 23 Jul 2014 01:05:43 +0000
treeherdermozilla-central@5683746bac22 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerssmaug
bugs1040080
milestone34.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1040080 - Update nsIMessageManager.idl notes about in-process child process message manager. r=smaug
content/base/public/nsIMessageManager.idl
--- a/content/base/public/nsIMessageManager.idl
+++ b/content/base/public/nsIMessageManager.idl
@@ -120,37 +120,39 @@ interface nsIPrincipal;
  * ====================================================
  *
  * The second realm of message managers is the "process message
  * managers".  With one exception, these always correspond to process
  * boundaries.  The picture looks like
  *
  *  Parent process                      Child processes
  * ----------------                    -----------------
- *  global PPMM
+ *  global (GPPMM)
  *   |
- *   +<----> child PPMM
+ *   +-->parent in-process PIPMM<-->child in-process CIPPMM
  *   |
- *   +-->parent PMM1<------------------>child process CMM1
+ *   +-->parent (PPMM1)<------------------>child (CPMM1)
  *   |
- *   +-->parent PMM2<------------------>child process PMM2
+ *   +-->parent (PPMM2)<------------------>child (CPMM2)
  *   ...
  *
- * For example: the parent-process PMM1 sends messages directly to
- * only the child-process CMM1.
+ * Note, PIPMM and CIPPMM both run in the parent process.
  *
- * For example: CMM1 sends messages directly to PMM1.  The global PPMM
+ * For example: the parent-process PPMM1 sends messages to the
+ * child-process CPMM1.
+ *
+ * For example: CPMM1 sends messages directly to PPMM1. The global GPPMM
  * will also notify their message listeners when the message arrives.
  *
- * For example: messages sent through the global PPMM will be
- * dispatched to the listeners of the same-process, "child PPMM".
- * They will also be broadcast to PPM1, PPM2, etc.
+ * For example: messages sent through the global GPPMM will be
+ * dispatched to the listeners of the same-process, CIPPMM, CPMM1,
+ * CPMM2, etc.
  *
  *   ***** PERFORMANCE AND SECURITY WARNING *****
- * Messages broadcast through the global PPMM can result in messages
+ * Messages broadcast through the GPPMM can result in messages
  * being dispatched across many OS processes, and to many processes
  * with different permissions.  Great care should be taken when
  * broadcasting.
  *
  * Requests sent to parent-process message listeners should usually
  * have replies scoped to the requesting CPMM.  The following pattern
  * is common
  *