W3C home > Mailing lists > Public > public-html-commits@w3.org > April 2009

html5/eventsource Overview.html,1.27,1.28

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 26 Apr 2009 23:29:03 +0000
To: public-html-commits@w3.org
Message-Id: <E1LyDmR-0004qC-Tq@lionel-hutz.w3.org>
Update of /sources/public/html5/eventsource
In directory hutz:/tmp/cvs-serv18594

Modified Files:
Log Message:
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) (whatwg r2993)

Index: Overview.html
RCS file: /sources/public/html5/eventsource/Overview.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -d -r1.27 -r1.28
--- Overview.html	26 Apr 2009 22:10:52 -0000	1.27
+++ Overview.html	26 Apr 2009 23:29:01 -0000	1.28
@@ -318,8 +318,17 @@
    <li><p>Return a new <code><a href="#eventsource">EventSource</a></code> object, and continue
    these steps in the background (without blocking scripts).</li>
-   <li><p><span>Fetch</span> the resource identified by the resulting
-   <span>absolute URL</span>, as described below.</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 id="dom-eventsource-url" title="dom-EventSource-URL"><code>URL</code></dfn>
   attribute must return the <span>absolute URL</span> that resulted
@@ -694,7 +703,8 @@
   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><a href="#eventsource">EventSource</a></code>
-  functionality on a per-page basis.<hr><p>Other formats of event framing may also be supported in addition
+  functionality on a per-page basis, or by sharing a single
+  <code><a href="#eventsource">EventSource</a></code> object using a <span title="SharedWorkerGlobalScope">shared worker</span>.<hr><p>Other formats of event framing may also be supported in addition
   to <code>text/event-stream</code>, but this specification does not
   define how they are to be parsed or processed.<p class="note">Such formats could include systems like SMS-push;
   for example servers could use <code title="">Accept</code> headers
Received on Sunday, 26 April 2009 23:29:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:09:21 UTC