[html5] r4398 - [e] (0) Remove completely bogus example.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-12-03 03:49:46 -0800 (Thu, 03 Dec 2009)
New Revision: 4398

Modified:
   complete.html
   index
   source
Log:
[e] (0) Remove completely bogus example.

Modified: complete.html
===================================================================
--- complete.html	2009-12-03 11:01:28 UTC (rev 4397)
+++ complete.html	2009-12-03 11:49:46 UTC (rev 4398)
@@ -67144,29 +67144,9 @@
   server, port, and path, instead of relying on the server to verify
   that the requested host, port, and path are correct.</p>
 
-  <div class=example>
 
-   <p>For example, consider a server running on port 20000 of a shared
-   virtual host, on behalf of the author of www.example.com, which is
-   hosted on that server. The author of the site hostile.example.net,
-   also hosted on the same server, could write a script to connect to
-   port 20000 on hostile.example.net; if neither the client nor the
-   server verified that all was well, this would connect, and the
-   author of the site hostile.example.net could then use the resources
-   of www.example.com.</p>
 
-   <p>With the Web Socket protocol, though, the server responds with a
-   <code>WebSocket-Location</code> header in the handshake, explicitly
-   saying that it is serving <code title="">ws://www.example.com:20000/</code>. The client, expecting
-   (in the case of its use by the hostile author) that the
-   <code>WebSocket-Location</code> be <code title="">ws://hostile.example.net:20000/</code>, would abort the
-   connection.</p>
 
-  </div>
-
-
-
-
   <h5 id=using-the-web-socket-protocol-from-other-specifications><span class=secno>10.3.4.8 </span>Using the Web Socket protocol from other specifications</h5>
 
   <p>The Web Socket protocol is intended to be used by another
@@ -86747,6 +86727,7 @@
   Tommy Thorsen,
   Travis Leithead,
   Tyler Close,
+  Vladimir Katardjiev,
   Vladimir Vukićević,
   voracity,
   Wakaba,

Modified: index
===================================================================
--- index	2009-12-03 11:01:28 UTC (rev 4397)
+++ index	2009-12-03 11:49:46 UTC (rev 4398)
@@ -78591,6 +78591,7 @@
   Tommy Thorsen,
   Travis Leithead,
   Tyler Close,
+  Vladimir Katardjiev,
   Vladimir Vukićević,
   voracity,
   Wakaba,

Modified: source
===================================================================
--- source	2009-12-03 11:01:28 UTC (rev 4397)
+++ source	2009-12-03 11:49:46 UTC (rev 4398)
@@ -76612,31 +76612,9 @@
   server, port, and path, instead of relying on the server to verify
   that the requested host, port, and path are correct.</p>
 
-  <div class="example">
 
-   <p>For example, consider a server running on port 20000 of a shared
-   virtual host, on behalf of the author of www.example.com, which is
-   hosted on that server. The author of the site hostile.example.net,
-   also hosted on the same server, could write a script to connect to
-   port 20000 on hostile.example.net; if neither the client nor the
-   server verified that all was well, this would connect, and the
-   author of the site hostile.example.net could then use the resources
-   of www.example.com.</p>
 
-   <p>With the Web Socket protocol, though, the server responds with a
-   <code>WebSocket-Location</code> header in the handshake, explicitly
-   saying that it is serving <code
-   title="">ws://www.example.com:20000/</code>. The client, expecting
-   (in the case of its use by the hostile author) that the
-   <code>WebSocket-Location</code> be <code
-   title="">ws://hostile.example.net:20000/</code>, would abort the
-   connection.</p>
 
-  </div>
-
-
-
-
   <h5>Using the Web Socket protocol from other specifications</h5>
 
   <p>The Web Socket protocol is intended to be used by another
@@ -97012,6 +96990,7 @@
   Tommy Thorsen,
   Travis Leithead,
   Tyler Close,
+  Vladimir Katardjiev,
   Vladimir Vuki&#x0107;evi&#x0107;,
   voracity,
   Wakaba,