W3C home > Mailing lists > Public > public-html-diffs@w3.org > February 2009

spec/Overview.html 1.2022 2851 Mark the semantics of cross-origin event

From: poot <cvsmail@w3.org>
Date: Mon, 23 Feb 2009 17:06:03 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090223080603.CDAA72BC00@toro.w3.mag.keio.ac.jp>
Mark the semantics of cross-origin event sources as work-in-progress.
(whatwg r2851)

last event ID string
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2022.html#concept-event-stream-last-event-id

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2021&r2=1.2022&f=h
http://html5.org/tools/web-apps-tracker?from=2850&to=2851

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2021
retrieving revision 1.2022
diff -u -d -r1.2021 -r1.2022
--- Overview.html	23 Feb 2009 07:56:28 -0000	1.2021
+++ Overview.html	23 Feb 2009 08:02:55 -0000	1.2022
@@ -37198,15 +37198,12 @@
   sources.<p>If the event source's last event ID string is not the empty
   string, then a <code title="">Last-Event-ID</code> HTTP header must
   be included with the request, whose value is the value of the event
-  source's last event ID string.<p>For connections to domains other than <a href=#the-document-s-domain>the document's
-  domain</a>, the semantics of the Access-Control HTTP header must
-  be followed. <a href=#references>[ACCESSCONTROL]</a> <!--
-  XXX define this better once that spec is more stable -->
-
-  <p>HTTP 200 OK responses with a <a href=#content-type-0>Content-Type</a> header
-  specifying the type <code>text/event-stream</code> that are either
-  from <a href=#the-document-s-domain>the document's domain</a> or explicitly allowed by the
-  Access-Control HTTP headers must be processed line by line <a href=#event-stream-interpretation>as described below</a>.<p>For the purposes of such successfully opened event streams only,
+  source's last event ID string.<p class=XXX>Cross-origin loads are expected to follow the
+  Access-Control semantics of CORS; without this header, they are
+  expected to fail as if the site was down.<p>HTTP 200 OK responses with a <a href=#content-type-0>Content-Type</a> header
+  specifying the type <code>text/event-stream</code> must be processed
+  line by line <a href=#event-stream-interpretation>as described
+  below</a>.<p>For the purposes of such successfully opened event streams only,
   user agents should ignore HTTP cache headers, and instead assume
   that the resource indicates that it does not wish to be cached.<p>If such a resource (with the correct MIME type) completes loading
   (i.e. the entire HTTP response body is received or the connection
@@ -37214,9 +37211,8 @@
   resource again after a delay equal to the reconnection time of the
   event source. This doesn't apply for the error cases that are listed
   below.<p>HTTP 200 OK responses that have a <a href=#content-type-0>Content-Type</a> other
-  than <code>text/event-stream</code> (or some other supported type),
-  and HTTP responses whose Access-Control headers indicate that the
-  resource are not to be used, must be ignored.<p>HTTP 204 No Content, and 205 Reset Content responses must be
+  than <code>text/event-stream</code> (or some other supported type)
+  must be ignored.<p>HTTP 204 No Content, and 205 Reset Content responses must be
   treated as if they were 200 OK responses with the right MIME type
   but no content, and should therefore cause the user agent to refetch
   the resource after a delay equal to the reconnection time of the
Received on Monday, 23 February 2009 08:06:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:13:58 GMT