From 761587c962174caca2efa2fce065ebbd930be763 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Mon, 19 Oct 2009 16:44:50 -0700 Subject: README: change ordering of concurrency model listing 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!). --- README | 4 ++-- 1 file 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 -- cgit v1.2.3-24-ge0c7