From 47e95cbf4a3e3112f6c393161039d8871c5e7b1e Mon Sep 17 00:00:00 2001
From: Ryan Dahl <ry@tinyclouds.org>
Date: Sun, 3 Apr 2011 11:34:07 -0700
Subject: [PATCH] iocp-links: clean up introduction

---
 iocp-links.html | 35 +++++++++++++----------------------
 1 file changed, 13 insertions(+), 22 deletions(-)

diff --git a/iocp-links.html b/iocp-links.html
index c2d828e9f..d93f65374 100644
--- a/iocp-links.html
+++ b/iocp-links.html
@@ -45,35 +45,26 @@
 <p>This document assumes you are familiar with how non-blocking socket I/O
 is done in Unix.
 
-<p>Windows presents asynchronous and non-blocking I/O differently than in Unix.
-The syscall
-<a href="http://msdn.microsoft.com/en-us/library/ms740141(v=VS.85).aspx"><code>select()</code>
-  is available in Windows</a>.
-<code>select</code> processing is O(n) in the number of file descriptors
-unlike the modern constant-time multiplexers like epoll which makes it
+<p>The syscall
+<a href="http://msdn.microsoft.com/en-us/library/ms740141(v=VS.85).aspx"><code>select</code>
+  is available in Windows</a> 
+but <code>select</code> processing is O(n) in the number of file descriptors
+unlike the modern constant-time multiplexers like epoll which makes select
 unacceptable for high-concurrency servers.
+This document will describe how high-concurrency programs are
+designed in Windows.
 
 <p>
-Windows has another way of polling called
+Instead of <a href="http://en.wikipedia.org/wiki/Epoll">epoll</a>
+or
+<a href="http://en.wikipedia.org/wiki/Kqueue">kqueue</a>,
+Windows has its own I/O multiplexer  called
 <a href="http://msdn.microsoft.com/en-us/library/aa365198(VS.85).aspx">I/O completion ports</a>
 (IOCPs). IOCPs are the objects used to poll
 <a href="http://msdn.microsoft.com/en-us/library/ms686358(v=vs.85).aspx">overlapped I/O</a>
 for completion. IOCP polling is constant time (REF?).
-They are similar to the Unix I/O multiplexers
-<ul>
-  <li> <a
-  href="http://en.wikipedia.org/wiki/Kqueue">kqueue</a> on Macintosh and
-BSDs,
-  <li> <a href="http://en.wikipedia.org/wiki/Epoll">epoll</a>
-  on Linux,
-  <li> <a
-  href="http://developers.sun.com/solaris/articles/event_completion.html">event
-  completion ports</a> on Solaris,
-  <li> <a href="">poll</a> on modern Unixes, and
-  <li> <a
-    href="http://www.kernel.org/doc/man-pages/online/pages/man2/select.2.html"><code>select()</code></a>,
-  which is available everywhere.
-</ul>
+
+<p>
 The fundamental variation is that in a Unix you generally ask the kernel to
 wait for state change in a file descriptor's readability or writablity. With
 overlapped I/O and IOCPs the programmers waits for asynchronous function