[html5] r5244 - [giow] (1) Clarify that these integers are unsigned.

whatwg at whatwg.org whatwg at whatwg.org
Thu Aug 5 18:16:35 PDT 2010


Author: ianh
Date: 2010-08-05 18:16:34 -0700 (Thu, 05 Aug 2010)
New Revision: 5244

Modified:
   complete.html
   source
Log:
[giow] (1) Clarify that these integers are unsigned.

Modified: complete.html
===================================================================
--- complete.html	2010-08-06 01:04:07 UTC (rev 5243)
+++ complete.html	2010-08-06 01:16:34 UTC (rev 5244)
@@ -72827,8 +72827,8 @@
 
   <p>Data is sent in the form of UTF-8 text. Each frame of data starts
   with a 0xFF byte identifying the frame type, followed by the number
-  of bytes in the data expressed as a big-endian 64 bit integer,
-  followed by the UTF-8 data.</p>
+  of bytes in the data expressed as a big-endian 64 bit unsigned
+  integer, followed by the UTF-8 data.</p>
 
   <p class=note>The length is the number of UTF-8 <em>bytes</em>,
   and not the number of characters. For example, the string
@@ -73709,8 +73709,8 @@
    <li>
 
     <p>Let <var title="">key<sub>3</sub></var> be a string consisting
-    of eight random bytes (or equivalently, a random 64 bit integer
-    encoded in big-endian order).</p>
+    of eight random bytes (or equivalently, a random 64 bit unsigned
+    integer encoded in big-endian order).</p>
 
     <p class=example>For example, 0x47 0x30 0x22 0x2D 0x5A 0x3F 0x47
     0x58.</p>
@@ -74251,7 +74251,7 @@
    <li>
 
     <p>Try to read eight more bytes from the server. Let <var title="">frame length</var> be the result of interpreting those
-    eight bytes as a big-endian 64 bit integer.</p>
+    eight bytes as a big-endian 64 bit unsigned integer.</p>
 
    </li>
 
@@ -74358,8 +74358,8 @@
 
    <li><p>Send a 0xFF byte to the server.</li>
 
-   <li><p>Send the number of bytes in <var title="">bytes</var>, as
-   a 64 bit big-endian integer, to the server.</li>
+   <li><p>Send the number of bytes in <var title="">bytes</var>, as a
+   64 bit big-endian unsigned integer, to the server.</li>
 
    <li><p>Send <var title="">raw data</var> to the server.</li>
 
@@ -74935,7 +74935,7 @@
    <li>
 
     <p>Try to read eight more bytes from the client. Let <var title="">frame length</var> be the result of interpreting those
-    eight bytes as a big-endian 64 bit integer.</p>
+    eight bytes as a big-endian 64 bit unsigned integer.</p>
 
    </li>
 
@@ -75003,7 +75003,7 @@
    <li><p>Send a 0xFF byte to the client.</li>
 
    <li><p>Send the number of bytes in <var title="">raw data</var>, as
-   a 64 bit big-endian integer, to the client.</li>
+   a 64 bit big-endian unsigned integer, to the client.</li>
 
    <li><p>Send <var title="">raw data</var> to the client.</li>
 

Modified: source
===================================================================
--- source	2010-08-06 01:04:07 UTC (rev 5243)
+++ source	2010-08-06 01:16:34 UTC (rev 5244)
@@ -81943,8 +81943,8 @@
 
   <p>Data is sent in the form of UTF-8 text. Each frame of data starts
   with a 0xFF byte identifying the frame type, followed by the number
-  of bytes in the data expressed as a big-endian 64 bit integer,
-  followed by the UTF-8 data.</p>
+  of bytes in the data expressed as a big-endian 64 bit unsigned
+  integer, followed by the UTF-8 data.</p>
 
   <p class="note">The length is the number of UTF-8 <em>bytes</em>,
   and not the number of characters. For example, the string
@@ -82937,8 +82937,8 @@
    <li>
 
     <p>Let <var title="">key<sub>3</sub></var> be a string consisting
-    of eight random bytes (or equivalently, a random 64 bit integer
-    encoded in big-endian order).</p>
+    of eight random bytes (or equivalently, a random 64 bit unsigned
+    integer encoded in big-endian order).</p>
 
     <p class="example">For example, 0x47 0x30 0x22 0x2D 0x5A 0x3F 0x47
     0x58.</p>
@@ -83549,7 +83549,7 @@
 
     <p>Try to read eight more bytes from the server. Let <var
     title="">frame length</var> be the result of interpreting those
-    eight bytes as a big-endian 64 bit integer.</p>
+    eight bytes as a big-endian 64 bit unsigned integer.</p>
 
    </li>
 
@@ -83673,8 +83673,8 @@
 
    <li><p>Send a 0xFF byte to the server.</p></li>
 
-   <li><p>Send the number of bytes in <var title="">bytes</var>, as
-   a 64 bit big-endian integer, to the server.</p></li>
+   <li><p>Send the number of bytes in <var title="">bytes</var>, as a
+   64 bit big-endian unsigned integer, to the server.</p></li>
 
    <li><p>Send <var title="">raw data</var> to the server.</p></li>
 
@@ -84311,7 +84311,7 @@
 
     <p>Try to read eight more bytes from the client. Let <var
     title="">frame length</var> be the result of interpreting those
-    eight bytes as a big-endian 64 bit integer.</p>
+    eight bytes as a big-endian 64 bit unsigned integer.</p>
 
    </li>
 
@@ -84390,7 +84390,7 @@
    <li><p>Send a 0xFF byte to the client.</p></li>
 
    <li><p>Send the number of bytes in <var title="">raw data</var>, as
-   a 64 bit big-endian integer, to the client.</p></li>
+   a 64 bit big-endian unsigned integer, to the client.</p></li>
 
    <li><p>Send <var title="">raw data</var> to the client.</p></li>
 




More information about the Commit-Watchers mailing list