[html5] r4123 - [e] (0) Ack for last checkin, and note for feature in future versions.

whatwg at whatwg.org whatwg at whatwg.org
Tue Oct 13 00:23:36 PDT 2009


Author: ianh
Date: 2009-10-13 00:23:34 -0700 (Tue, 13 Oct 2009)
New Revision: 4123

Modified:
   complete.html
   index
   source
Log:
[e] (0) Ack for last checkin, and note for feature in future versions.

Modified: complete.html
===================================================================
--- complete.html	2009-10-13 05:49:02 UTC (rev 4122)
+++ complete.html	2009-10-13 07:23:34 UTC (rev 4123)
@@ -65335,6 +65335,22 @@
    <a href=#concept-event-stream-reconnection-time title=concept-event-stream-reconnection-time>reconnection
    time</a> to that integer. Otherwise, ignore the field.</dd>
 
+   <!-- v2 feature request from Per-Erik Brodin:
+      > > > Finally, it could be useful to be able to reset the reconnection
+      > > > time to the user agent default value by sending the retry field only
+      > > > and leave out the value similar to how you reset the last event id.
+      > >
+      > > What's the use case?
+      >
+      > Take the stock ticker as an example. When the stock market closes the
+      > server logic knows that there won't be any new events for a number of
+      > hours and so it can send the corresponding reconnection time and close
+      > the connection. If the client is still running by the time the market
+      > opens, it will reconnect, and the server can now reset the reconnection
+      > time to a time that is convenient for the user agent (which is the user
+      > agent default value, unknown to the server).
+    -->
+
 <!-- v2 feature request from John Fallows - http://www.w3.org/mid/c5b3a7130810271238h11e40a4fybfcd5983ed5dc08d@mail.gmail.com
 
    <dt>If the field name is "reconnect"</dt>
@@ -85777,6 +85793,7 @@
   Olli Pettay,
   Patrick H. Lauke,
   Paul Norman,
+  Per-Erik Brodin,
   Peter Karlsson,
   Peter Kasting,
   Peter Stark,

Modified: index
===================================================================
--- index	2009-10-13 05:49:02 UTC (rev 4122)
+++ index	2009-10-13 07:23:34 UTC (rev 4123)
@@ -76762,6 +76762,7 @@
   Olli Pettay,
   Patrick H. Lauke,
   Paul Norman,
+  Per-Erik Brodin,
   Peter Karlsson,
   Peter Kasting,
   Peter Stark,

Modified: source
===================================================================
--- source	2009-10-13 05:49:02 UTC (rev 4122)
+++ source	2009-10-13 07:23:34 UTC (rev 4123)
@@ -73428,6 +73428,22 @@
    <span title="concept-event-stream-reconnection-time">reconnection
    time</span> to that integer. Otherwise, ignore the field.</p></dd>
 
+   <!-- v2 feature request from Per-Erik Brodin:
+      > > > Finally, it could be useful to be able to reset the reconnection
+      > > > time to the user agent default value by sending the retry field only
+      > > > and leave out the value similar to how you reset the last event id.
+      > >
+      > > What's the use case?
+      >
+      > Take the stock ticker as an example. When the stock market closes the
+      > server logic knows that there won't be any new events for a number of
+      > hours and so it can send the corresponding reconnection time and close
+      > the connection. If the client is still running by the time the market
+      > opens, it will reconnect, and the server can now reset the reconnection
+      > time to a time that is convenient for the user agent (which is the user
+      > agent default value, unknown to the server).
+    -->
+
 <!-- v2 feature request from John Fallows - http://www.w3.org/mid/c5b3a7130810271238h11e40a4fybfcd5983ed5dc08d@mail.gmail.com
 
    <dt>If the field name is "reconnect"</dt>
@@ -94589,6 +94605,7 @@
   Olli Pettay,
   Patrick H. Lauke,
   Paul Norman,
+  Per-Erik Brodin,
   Peter Karlsson,
   Peter Kasting,
   Peter Stark,




More information about the Commit-Watchers mailing list