about summary refs log tree commit homepage
path: root/README
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2009-11-27 10:21:43 -0800
committerEric Wong <normalperson@yhbt.net>2009-11-27 10:22:10 -0800
commit32b2b2a3669ba5b96d172acdcc6c8886609fff4d (patch)
tree58a8a82af567e27e27e2341850ba125d96cd9a44 /README
parentabe9ce1e677b88c5b1f4f04ba9759d6c272b8563 (diff)
downloadrainbows-32b2b2a3669ba5b96d172acdcc6c8886609fff4d.tar.gz
Diffstat (limited to 'README')
-rw-r--r--README41
1 files changed, 22 insertions, 19 deletions
diff --git a/README b/README
index 38932d4..10ed443 100644
--- a/README
+++ b/README
@@ -13,24 +13,22 @@ suck; differently.
 
 For network concurrency, models we currently support are:
 
-* {:Revactor}[link:Rainbows/Revactor.html]
-* {:ThreadPool}[link:Rainbows/ThreadPool.html]
-* {:Rev}[link:Rainbows/Rev.html]
-* {:ThreadSpawn}[link:Rainbows/ThreadSpawn.html]
-* {:EventMachine}[link:Rainbows/EventMachine.html]
-* {:RevThreadSpawn}[link:Rainbows/RevThreadSpawn.html]
-* {:FiberSpawn}[link:Rainbows/FiberSpawn.html]
-* {:FiberPool}[link:Rainbows/FiberPool.html]
-
-We have {more on the way}[link:TODO.html] for handling network concurrency.
-Additionally, we also use multiple processes (managed by Unicorn) for
-CPU/memory/disk concurrency.
-
-For application concurrency with Thread-based models, we have the
-Rainbows::AppPool Rack middleware that allows us to limit application
-concurrency independently of network concurrency.  Rack::Lock as
-distributed by Rack may also be used to limit application concurrency to
-one (per-worker).
+* {Revactor}[link:Rainbows/Revactor.html]
+* {ThreadPool}[link:Rainbows/ThreadPool.html]
+* {Rev}[link:Rainbows/Rev.html]
+* {ThreadSpawn}[link:Rainbows/ThreadSpawn.html]
+* {EventMachine}[link:Rainbows/EventMachine.html]
+* {RevThreadSpawn}[link:Rainbows/RevThreadSpawn.html]
+* {FiberSpawn}[link:Rainbows/FiberSpawn.html]
+* {FiberPool}[link:Rainbows/FiberPool.html]
+
+We have {many more on the way}[link:TODO.html] for handling network
+concurrency.  Additionally, we also use multiple processes (managed by
+Unicorn) for robustness and CPU/memory/disk concurrency.
+
+We also provide Rainbows::AppPool Rack middleware for some network
+concurrency models for limiting application concurrency independently of
+network concurrency.
 
 == Features
 
@@ -51,6 +49,9 @@ one (per-worker).
   be scaled independently of client connections.  More concurrency models
   (listed in the TODO) will be supported as we find time for them.
 
+* We give you {lots of options}[link:Summary.html] with more
+  {on the way}[link:TODO.html].
+
 == Applications
 
 \Rainbows is mainly designed for the odd things Unicorn sucks at:
@@ -63,7 +64,9 @@ one (per-worker).
 * BOSH (with slow clients)
 * HTTP server push
 * Long polling
-* Reverse Ajax
+* Reverse AJAX
+* HTML 5 Web Sockets
+* real-time upload processing
 
 \Rainbows can also be used to service slow clients directly even with
 fast applications.