about summary refs log tree commit homepage
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2009-10-27 00:25:11 -0700
committerEric Wong <normalperson@yhbt.net>2009-10-27 00:25:53 -0700
commit9e809dec64996ef461c31ee1d79b9317874bd34b (patch)
tree034d5f4b93c1ef3f3f837eabbfff474a9651dfd4
parentfcc18638d01f50ba02621a6eaa2cf11be47d4d26 (diff)
Now that we have EM support (which is basically like
Rev), update our docs for that.  Also, expand on why
Revactor isn't supported just yet...
-rw-r--r--lib/rainbows/app_pool.rb16
1 files changed, 10 insertions, 6 deletions
diff --git a/lib/rainbows/app_pool.rb b/lib/rainbows/app_pool.rb
index ccb0bdb..f4c22a2 100644
--- a/lib/rainbows/app_pool.rb
+++ b/lib/rainbows/app_pool.rb
@@ -39,14 +39,18 @@ module Rainbows
   # AppPool should be used if you want to enforce a lower value of +P+
   # than +N+.
   #
-  # AppPool has no effect on the Rev concurrency model as that is
-  # single-threaded/single-instance as far as application concurrency goes.
-  # In other words, +P+ is always +one+ when using Rev.  AppPool currently
-  # only works with the ThreadSpawn and ThreadPool models.  It does not
-  # yet work reliably with the Revactor model, yet.
+  # AppPool has no effect on the Rev or EventMachine concurrency models
+  # as those are single-threaded/single-instance as far as application
+  # concurrency goes.  In other words, +P+ is always +one+ when using
+  # Rev or EventMachine.  AppPool currently only works with the
+  # ThreadSpawn and ThreadPool models.  It does not yet work reliably
+  # with the Revactor model, but actors are far more lightweight and
+  # probably better suited for lightweight applications that would
+  # not benefit from AppPool.
   #
   # Since this is Rack middleware, you may load this in your Rack
-  # config.ru file and even use it in servers other than \Rainbows!
+  # config.ru file and even use it in threaded servers other than
+  # \Rainbows!
   #
   #   use Rainbows::AppPool, :size => 30
   #   map "/lobster" do