html5/webstorage Overview.html,1.72,1.73

Update of /sources/public/html5/webstorage
In directory hutz:/tmp/cvs-serv27917

Modified Files:
	Overview.html 
Log Message:
Integrate with draft-abarth-cookie-03. (whatwg r3740)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/webstorage/Overview.html,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -d -r1.72 -r1.73
--- Overview.html	31 Aug 2009 10:10:21 -0000	1.72
+++ Overview.html	3 Sep 2009 12:13:01 -0000	1.73
@@ -173,7 +173,7 @@
    <h1>Web Storage</h1>
    <!--ZZZ:-->
    <!--<h2 class="no-num no-toc">W3C Working Draft 23 April 2009</h2>-->
-   <h2 class="no-num no-toc" id="editor-s-draft-31-august-2009">Editor's Draft 31 August 2009</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-3-september-2009">Editor's Draft 3 September 2009</h2>
    <!--:ZZZ-->
    <dl><!-- ZZZ: update the month/day (twice), (un)comment out
     <dt>This Version:</dt>
@@ -240,7 +240,7 @@
   specification's progress along the W3C Recommendation track.
   <!--ZZZ:-->
   <!--This specification is the 23 April 2009 Working Draft.-->
-  This specification is the 31 August 2009 Editor's Draft.
+  This specification is the 3 September 2009 Editor's Draft.
   <!--:ZZZ-->
   </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
@@ -280,7 +280,7 @@
  <li><a class="no-num" href="#references">References</a></ol>
 <!--end-toc--><hr><h2 id="introduction"><span class="secno">1 </span>Introduction</h2><p><i>This section is non-normative.</i><p>This specification introduces two related mechanisms, similar to
   HTTP session cookies, for storing structured data on the client
-  side. <a href="#refsRFC2109">[RFC2109]</a> <a href="#refsCOOKIES">[COOKIES]</a><p>The first is designed for scenarios where the user is carrying
+  side. <a href="#refsCOOKIES">[COOKIES]</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 different windows at the same time.<p>Cookies don't really handle this case well. For example, a user
   could be buying plane tickets in two different windows, using the
@@ -685,7 +685,7 @@
     
     persistent storage feature
     to the user in a way that does not distinguish them from HTTP
-    session cookies. <a href="#refsRFC2109">[RFC2109]</a> <a href="#refsCOOKIES">[COOKIES]</a></p>
+    session cookies. <a href="#refsCOOKIES">[COOKIES]</a></p>
 
     <p>This might encourage users to view such storage with healthy
     suspicion.</p>
@@ -831,10 +831,6 @@
    <dd><cite><a href="http://www.whatwg.org/specs/web-apps/current-work/">HTML5</a></cite>,
    I. Hickson. WHATWG, August 2009.</dd>
 
-   <dt id="refsRFC2109">[RFC2109]</dt>
-   <dd><cite><a href="http://www.ietf.org/rfc/rfc2109.txt">HTTP State Management
-   Mechanism</a></cite>, D. Kristol, L. Montulli. IETF, February 1997.</dd>
-
    <dt id="refsRFC2119">[RFC2119]</dt>
    <dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in
    RFCs to Indicate Requirement Levels</a></cite>, S. Bradner. IETF, March

Received on Thursday, 3 September 2009 12:13:11 UTC