[e] (0) Make a note of the ills of PortCollection

Affected topics: DOM APIs

git-svn-id: http://svn.whatwg.org/webapps@8216 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -84288,6 +84288,10 @@ <h4 id=message-ports><span class=secno>10.5.3 </span>Message ports</h4>
 
   <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

index

@@ -84288,6 +84288,10 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {
 
   <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

source

@@ -94056,6 +94056,10 @@ interface <dfn>MessageChannel</dfn> {
 
   <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