html5/spec Overview.html,1.1036,1.1037

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv20135

Modified Files:
	Overview.html 
Log Message:
Make HTML5 agnostic regarding Cookie and Cookie2. (Re: Web Sockets) (credit: ns) (whatwg r1848)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1036
retrieving revision 1.1037
diff -u -d -r1.1036 -r1.1037
--- Overview.html	3 Jul 2008 20:52:53 -0000	1.1036
+++ Overview.html	6 Jul 2008 00:08:58 -0000	1.1037
@@ -59,7 +59,7 @@
     for HTML and XHTML</h2>
 
    <h2 class="no-num no-toc" id=editors0><!-- "W3C Working Draft" -->
-    Editor's Draft <!--ZZZ--> 3 July 2008</h2>
+    Editor's Draft <!--ZZZ--> 6 July 2008</h2>
 
    <dl><!-- ZZZ: update the month/day
     <dt>This Version:</dt>
@@ -207,7 +207,7 @@
 
   <p>The W3C <a href="http://www.w3.org/html/wg/">HTML Working Group</a> is
    the W3C working group responsible for this specification's progress along
-   the W3C Recommendation track. <!--ZZZ:--> This specification is the 3 July
+   the W3C Recommendation track. <!--ZZZ:--> This specification is the 6 July
    2008 <!--ZZZ "Working Draft"-->Editor's Draft. <!--:ZZZ--></p>
   <!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST -->
   <!-- relationship to other work (required) -->
@@ -6740,8 +6740,9 @@
    must return the same string as the value of the <code
    title="">Cookie</code> HTTP header it would include if fetching the
    resource indicated by <span>the document's
-   address</span><!-- XXXDOCURL --> over HTTP, as per RFC 2109 section 4.3.4.
-   <a href="#references">[RFC2109]</a>
+   address</span><!-- XXXDOCURL --> over HTTP, as per RFC 2109 section 4.3.4
+   or later specifications. <a href="#references">[RFC2109]</a> <a
+   href="#references">[RFC2965]</a>
 
   <p>On setting, if the <a href="#sandboxed2">sandboxed origin browsing
    context flag</a> is set on the <a href="#browsing1">browsing context</a>
@@ -6750,8 +6751,8 @@
    processing cookies if it had just attempted to fetch <span>the document's
    address</span><!-- XXXDOCURL --> over HTTP, and had received a response
    with a <code>Set-Cookie</code> header whose value was the specified value,
-   as per RFC 2109 sections 4.3.1, 4.3.2, and 4.3.3. <a
-   href="#references">[RFC2109]</a>
+   as per RFC 2109 sections 4.3.1, 4.3.2, and 4.3.3 or later specifications.
+   <a href="#references">[RFC2109]</a> <a href="#references">[RFC2965]</a>
 
   <p class=note>Since the <code title=dom-document-cookie><a
    href="#cookie0">cookie</a></code> attribute is accessible across frames,
@@ -35247,7 +35248,7 @@
 
   <p>This specification introduces two related mechanisms, similar to HTTP
    session cookies, for storing structured data on the client side. <a
-   href="#references">[RFC2965]</a> <a href="#references">[RFC2109]</a>
+   href="#references">[RFC2109]</a> <a href="#references">[RFC2965]</a>
 
   <p>The first is designed for scenarios where the user is carrying out a
    single transaction, but could be carrying out multiple transactions in
@@ -36296,7 +36297,7 @@
     <p>Treating persistent storage as cookies: user agents should present the
      persistent storage and database features to the user in a way that does
      not distinguish them from HTTP session cookies. <a
-     href="#references">[RFC2965]</a> <a href="#references">[RFC2109]</a></p>
+     href="#references">[RFC2109]</a> <a href="#references">[RFC2965]</a></p>
 
     <p>This might encourage users to view persistent storage with healthy
      suspicion.</p>
@@ -36629,7 +36630,7 @@
   <p>User agents must ignore any entity bodies returned in the responses, but
    must, unless otherwise specified by the user, honor the HTTP headers
    (including, in particular, redirects and HTTP cookie headers). <a
-   href="#references">[RFC2965]</a> <a href="#references">[RFC2109]</a>
+   href="#references">[RFC2109]</a> <a href="#references">[RFC2965]</a>
 
   <p>When the <code title=attr-hyperlink-ping><a href="#ping">ping</a></code>
    attribute is present, user agents should clearly indicate to the user that
@@ -41699,7 +41700,7 @@
      true and is otherwise identical to <var title="">url</var>, then HTTP
      headers that would be appropriate for that information should be sent at
      this point. <a href="#references">[RFC2616]</a> <a
-     href="#references">[RFC2965]</a> <a href="#references">[RFC2109]</a></p>
+     href="#references">[RFC2109]</a> <a href="#references">[RFC2965]</a></p>
 
     <p>Each header must be on a line of its own (each ending with a CR LF
      sequence). For the purposes of this step, each header must not be split
@@ -41898,7 +41899,7 @@
       <code title="">http</code> if <var title="">secure</var> is false and
       <code title="">https</code> if <var title="">secure</var> is true and
       is otherwise identical to <var title="">url</var>. <a
-      href="#references">[RFC2965]</a> <a href="#references">[RFC2109]</a>
+      href="#references">[RFC2109]</a> <a href="#references">[RFC2965]</a>
 
      <dt>Any other name

Received on Sunday, 6 July 2008 00:09:37 UTC