Fix the garbage collection rules for ports to actually make sense, and add a note for authors urging them not to rely on the gc for ports. (whatwg r3227)

Fix the garbage collection rules for ports to actually make sense, and
add a note for authors urging them not to rely on the gc for ports.
(whatwg r3227)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2375&r2=1.2376&f=h
http://html5.org/tools/web-apps-tracker?from=3226&to=3227

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2375
retrieving revision 1.2376
diff -u -d -r1.2375 -r1.2376
--- Overview.html 12 Jun 2009 01:18:00 -0000 1.2375
+++ Overview.html 12 Jun 2009 03:22:11 -0000 1.2376
@@ -52488,15 +52488,13 @@
   as if the <code title="dom-MessagePort-start"><a href="#dom-messageport-start">start()</a></code> method
   had been called.</p>
 
-  </div><div class="impl">
-
-  <h5 id="ports-and-garbage-collection"><span class="secno">8.3.3.1 </span>Ports and garbage collection</h5>
+  </div><h5 id="ports-and-garbage-collection"><span class="secno">8.3.3.1 </span>Ports and garbage collection</h5><div class="impl">
 
-  <p>When a <code><a href="#messageport">MessagePort</a></code> object is entangled, user agents
-  must either act as if the object has a strong reference to its
-  entangled <code><a href="#messageport">MessagePort</a></code> object, or as if the
-  <code><a href="#messageport">MessagePort</a></code> object's owner has a strong reference to
-  the <code><a href="#messageport">MessagePort</a></code> object.</p>
+  <p>When a <code><a href="#messageport">MessagePort</a></code> object <var title="">o</var> is
+  entangled, user agents must either act as if <var title="">o</var>'s
+  entangled <code><a href="#messageport">MessagePort</a></code> object has a strong reference to
+  <var title="">o</var>, or as if <var title="">o</var>'s owner has a
+  strong reference to <var title="">o</var>.</p>
 
   <div class="note">
 
@@ -52524,7 +52522,11 @@
   <!-- XXX what about ports in the ports attribute of a MessageEvent
   that isn't dispatched yet? -->
 
-  </div><h2 id="syntax"><span class="secno">9 </span><dfn>The HTML syntax</dfn></h2><p class="note">This section only describes the rules for <code title="">text/html</code> resources. Rules for XML resources are
+  </div><p class="note">Authors are strongly encouraged to explicitly close
+  <code><a href="#messageport">MessagePort</a></code> objects to disentangle them, so that their
+  resources can be recollected. Creating many <code><a href="#messageport">MessagePort</a></code>
+  objects and discarding them without closing them can lead to high
+  memory usage.<h2 id="syntax"><span class="secno">9 </span><dfn>The HTML syntax</dfn></h2><p class="note">This section only describes the rules for <code title="">text/html</code> resources. Rules for XML resources are
   discussed in the section below entitled "<a href="#the-xhtml-syntax">The XHTML
   syntax</a>".<h3 id="writing-html-documents"><span class="secno">9.1 </span>Writing HTML documents</h3><div class="impl">

Received on Friday, 12 June 2009 03:23:03 UTC