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

html5/eventsource Overview.html,1.93,1.94

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 01 Dec 2009 06:47:59 +0000
To: public-html-commits@w3.org
Message-Id: <E1NFMWl-0004va-4t@lionel-hutz.w3.org>
Update of /sources/public/html5/eventsource
In directory hutz:/tmp/cvs-serv18924

Modified Files:
	Overview.html 
Log Message:
Minor clarifications (whatwg r4385)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/eventsource/Overview.html,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -d -r1.93 -r1.94
--- Overview.html	25 Nov 2009 10:55:47 -0000	1.93
+++ Overview.html	1 Dec 2009 06:47:56 -0000	1.94
@@ -169,7 +169,7 @@
    <p><a href="http://www.w3.org/"><img alt="W3C" height="48" src="http://www.w3.org/Icons/w3c_home" width="72"></a></p>
    <h1>Server-Sent Events</h1>
 
-   <h2 class="no-num no-toc" id="editor-s-draft-25-november-2009">Editor's Draft 25 November 2009</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-1-december-2009">Editor's Draft 1 December 2009</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/eventsource/">http://www.w3.org/TR/eventsource/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -231,7 +231,7 @@
   Working Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation track.
 
-  This specification is the 25 November 2009 Editor's Draft.
+  This specification is the 1 December 2009 Editor's Draft.
   </p><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
   February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/42538/status" rel="disclosure">public list of
   any patent disclosures</a> made in connection with the deliverables
@@ -769,9 +769,9 @@
   negative effects on the reliability of this protocol. Where
   possible, chunking should be disabled for serving event streams
   unless the rate of messages is high enough for this not to
-  matter.</p><!-- v2 can we get a better solution? --><p>Implementations that support HTTP's per-server connection
-  limitation might run into trouble when opening multiple pages from a
-  site if each page has an <code><a href="#eventsource">EventSource</a></code> to the same
+  matter.</p><!-- v2 can we get a better solution? --><p>Clients that support HTTP's per-server connection limitation
+  might run into trouble when opening multiple pages from a site if
+  each page has an <code><a href="#eventsource">EventSource</a></code> to the same
   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>
Received on Tuesday, 1 December 2009 06:48:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 December 2009 06:48:02 GMT