[html5] r2993 - [] (0) Make EventSource available to workers, and add some notes to EventSource' [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2009-04-26 16:28:58 -0700 (Sun, 26 Apr 2009)
New Revision: 2993

Modified:
   source
Log:
[] (0) Make EventSource available to workers, and add some notes to EventSource's definition that clarifies how to reduce the number of connections per server. (credit: jf)

Modified: source
===================================================================
--- source	2009-04-26 22:10:42 UTC (rev 2992)
+++ source	2009-04-26 23:28:58 UTC (rev 2993)
@@ -60862,6 +60862,9 @@
    <li><p>The <code>WebSocket</code> interface object and
    constructor. <a href="#refsWEBSOCKET">[WEBSOCKET]</a></p></li>
 
+   <li><p>The <code>EventSource</code> interface object and
+   constructor. <a href="#refsEVENTSOURCE">[EVENTSOURCE]</a></p></li>
+
    <li><p>The <code>MessageChannel</code> interface object and
    constructor. <a href="#refsHTML5">[HTML5]</a></p></li>
 
@@ -61098,9 +61101,19 @@
    <li><p>Return a new <code>EventSource</code> object, and continue
    these steps in the background (without blocking scripts).</p></li>
 
-   <li><p><span>Fetch</span> the resource identified by the resulting
-   <span>absolute URL</span>, as described below.</p></li>
+   <li>
 
+    <p><span>Fetch</span> the resource identified by the resulting
+    <span>absolute URL</span>, and process it as described below.</p>
+
+    <p class="note">The definition of the <span
+    title="fetch">fetching</span> algorithm is such that if the
+    browser is already fetching the resource identified by the given
+    <span>absolute URL</span>, that connection can be reused, instead
+    of a new connection being established.</p>
+
+   </li>
+
   </ol>
 
   <p>The <dfn title="dom-EventSource-URL"><code>URL</code></dfn>
@@ -61655,7 +61668,9 @@
   domain. Authors can avoid this using the relatively complex
   mechanism of using unique domain names per connection, or by
   allowing the user to enable or disable the <code>EventSource</code>
-  functionality on a per-page basis.</p>
+  functionality on a per-page basis, or by sharing a single
+  <code>EventSource</code> object using a <span
+  title="SharedWorkerGlobalScope">shared worker</span>.</p>
 
   <hr>