- From: CVS User ihickson <cvsmail@w3.org>
- Date: Wed, 09 Oct 2013 22:05:26 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/postmsg In directory roscoe:/tmp/cvs-serv2192 Modified Files: Overview.html Log Message: Make a note of the ills of PortCollection (whatwg r8216) --- /sources/public/html5/postmsg/Overview.html 2013/08/26 18:03:01 1.151 +++ /sources/public/html5/postmsg/Overview.html 2013/10/09 22:05:26 1.152 @@ -216,7 +216,7 @@ <h1>HTML5 Web Messaging</h1> - <h2 class="no-num no-toc" id="editor-s-draft-26-august-2013">Editor's Draft 26 August 2013</h2> + <h2 class="no-num no-toc" id="editor-s-draft-9-october-2013">Editor's Draft 9 October 2013</h2> <dl><dt>Latest Published Version:</dt> <dd><a href="http://www.w3.org/TR/webmessaging/">http://www.w3.org/TR/webmessaging/</a></dd> <dt>Latest Editor's Draft:</dt> @@ -348,7 +348,7 @@ </dl><p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications Working Group</a> is the W3C working group responsible for this specification's progress along the W3C Recommendation track. - This specification is the 26 August 2013 Editor's Draft. + This specification is the 9 October 2013 Editor's Draft. </p> @@ -1482,6 +1482,10 @@ <h3 id="broadcasting-to-many-ports"><span class="secno">5.4 </span>Broadcasting to many ports</h3> + <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
Received on Wednesday, 9 October 2013 22:05:27 UTC