From 04731323678eff58f709b36f864d12aa08cfe6d9 Mon Sep 17 00:00:00 2001
From: Christopher Faulet <christopher@yakaz.com>
Date: Wed, 14 Sep 2011 17:49:38 +0200
Subject: Explain how dynamic child processes are stopped

---
 system/doc/design_principles/sup_princ.xml | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'system')

diff --git a/system/doc/design_principles/sup_princ.xml b/system/doc/design_principles/sup_princ.xml
index 2748f21bbe..df0777559a 100644
--- a/system/doc/design_principles/sup_princ.xml
+++ b/system/doc/design_principles/sup_princ.xml
@@ -341,6 +341,10 @@ call:start_link(id1)</code>
 supervisor:terminate_child(Sup, Pid)</code>
     <p>where <c>Sup</c> is the pid, or name, of the supervisor and
     <c>Pid</c> is the pid of the child.</p>
+    <p>Because a <c>simple_one_for_one</c> supervisor could have many children,
+    it shuts them all down at same time. So, order in which they are stopped is
+    not defined. For the same reason, it could have an overhead with regards to
+    the <c>Shutdown</c> strategy.</p>
   </section>
 
   <section>
-- 
cgit v1.2.3