[html5] r8216 - [e] (0) Make a note of the ills of PortCollection Affected topics: DOM APIs

[whatwg at whatwg.org]

Author: ianh
Date: 2013-10-09 15:05:22 -0700 (Wed, 09 Oct 2013)
New Revision: 8216

Modified:
   complete.html
   index
   source
Log:
[e] (0) Make a note of the ills of PortCollection
Affected topics: DOM APIs

Modified: complete.html
===================================================================
--- complete.html	2013-10-09 18:46:54 UTC (rev 8215)
+++ complete.html	2013-10-09 22:05:22 UTC (rev 8216)
@@ -84288,6 +84288,10 @@
 
   <h4 id=broadcasting-to-many-ports><span class=secno>10.5.4 </span>Broadcasting to many ports</h4>
 
+  <p class=critical>The API described in this section is controversial, as, in an attempt to solve
+  an architectural memory leak, it instead exposes the details of Garbage Collection. This is a
+  lose-lose scenario. A better solution is really needed here.</p>
+
   <p>Broadcasting to many ports is in principle relatively simple: keep an array of
   <code><a href=#messageport>MessagePort</a></code> objects to send messages to, and iterate through the array to send a
   message. However, this has one rather unfortunate effect: it prevents the ports from being garbage

Modified: index
===================================================================
--- index	2013-10-09 18:46:54 UTC (rev 8215)
+++ index	2013-10-09 22:05:22 UTC (rev 8216)
@@ -84288,6 +84288,10 @@
 
   <h4 id=broadcasting-to-many-ports><span class=secno>10.5.4 </span>Broadcasting to many ports</h4>
 
+  <p class=critical>The API described in this section is controversial, as, in an attempt to solve
+  an architectural memory leak, it instead exposes the details of Garbage Collection. This is a
+  lose-lose scenario. A better solution is really needed here.</p>
+
   <p>Broadcasting to many ports is in principle relatively simple: keep an array of
   <code><a href=#messageport>MessagePort</a></code> objects to send messages to, and iterate through the array to send a
   message. However, this has one rather unfortunate effect: it prevents the ports from being garbage

Modified: source
===================================================================
--- source	2013-10-09 18:46:54 UTC (rev 8215)
+++ source	2013-10-09 22:05:22 UTC (rev 8216)
@@ -94056,6 +94056,10 @@
 
   <h4>Broadcasting to many ports</h4>
 
+  <p class="critical">The API described in this section is controversial, as, in an attempt to solve
+  an architectural memory leak, it instead exposes the details of Garbage Collection. This is a
+  lose-lose scenario. A better solution is really needed here.</p>
+
   <p>Broadcasting to many ports is in principle relatively simple: keep an array of
   <code>MessagePort</code> objects to send messages to, and iterate through the array to send a
   message. However, this has one rather unfortunate effect: it prevents the ports from being garbage