about summary refs log tree commit homepage
path: root/README
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2009-10-19 16:44:50 -0700
committerEric Wong <normalperson@yhbt.net>2009-10-19 16:53:00 -0700
commit761587c962174caca2efa2fce065ebbd930be763 (patch)
tree915109984f56971a7d57d4908ee30a4b1cb708ae /README
parent319f6ca5e72e9705cf0a20ae5a79c3d96ab823f2 (diff)
downloadrainbows-761587c962174caca2efa2fce065ebbd930be763.tar.gz
Revactor was our first take on the "rainbows" branch of Unicorn
and probably less confusing to people that may have tracked that
branch.  ThreadPool was used in the "gossamer" branch of Unicorn
before, but since this project is named Rainbows!, it's less
logical.  I'll freely admit to having some personal bias here
and not being a fan of threads (and especially not pthreads!).
Diffstat (limited to 'README')
-rw-r--r--README4
1 files changed, 2 insertions, 2 deletions
diff --git a/README b/README
index 4c76719..e7bc0c7 100644
--- a/README
+++ b/README
@@ -13,10 +13,10 @@ suck; differently.
 
 For network concurrency, models we currently support are:
 
-* {:ThreadSpawn}[link:Rainbows/ThreadSpawn.html]
-* {:ThreadPool}[link:Rainbows/ThreadPool.html]
 * {:Revactor}[link:Rainbows/Revactor.html]
+* {:ThreadPool}[link:Rainbows/ThreadPool.html]
 * {:Rev}[link:Rainbows/Rev.html]*
+* {:ThreadSpawn}[link:Rainbows/ThreadSpawn.html]
 
 We have {more on the way}[link:TODO.html] for handling network concurrency.
 Additionally, we also use multiple processes (managed by Unicorn) for