about summary refs log tree commit homepage
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2015-10-19 21:29:32 +0000
committerEric Wong <e@80x24.org>2015-10-19 21:29:50 +0000
commit3706ec9dce706d8cde76cafff1f3a24776435830 (patch)
tree95189ce8217cd5381507f1c68403034221de6b2c
parentf377d466ae7ca0d988f140606f2c2b658d5fdb97 (diff)
yahns runs as a single process just fine.
-rw-r--r--README9
1 files changed, 2 insertions, 7 deletions
diff --git a/README b/README
index 4ab955c..7b149ba 100644
--- a/README
+++ b/README
@@ -6,18 +6,13 @@ request/response times and/or slow clients.
 
 If you're on GNU/Linux and overwhelmed by options in \Rainbows!,
 consider {yahns}[http://yahns.yhbt.net/] as it has fewer options
-and more energy-efficient during non-peak traffic.
+and more energy-efficient during non-peak traffic and may also
+be configured as a single worker process.
 
 For Rack applications not heavily bound by slow external network
 dependencies, consider unicorn instead as it simpler and easier to
 debug.
 
-If you're on a small system, or write extremely tight and reliable code
-and don't want multiple worker processes, check out
-{Zbatery}[http://zbatery.bogomip.org/], too. Zbatery can use all the
-crazy network concurrency options of \Rainbows! in a single worker
-process.
-
 == \Rainbows! is about Diversity
 
 We aim to support as many concurrency models as we can because they all