Redirecting to http://rainbows.bogomips.org/Rainbows/CoolioThreadPool.html ...

Included Modules

Rainbows::CoolioThreadPool

A combination of the Coolio and ThreadPool models. This allows Ruby Thread-based concurrency for application processing. It DOES NOT expose a streamable “rack.input” for upload processing within the app. DevFdResponse should be used with this class to proxy asynchronous responses. All network I/O between the client and server are handled by the main thread and outside of the core application dispatch.

Unlike ThreadPool, Cool.io makes this model highly suitable for slow clients and applications with medium-to-slow response times (I/O bound), but less suitable for sleepy applications.

This concurrency model is designed for Ruby 1.9, and Ruby 1.8 users are NOT advised to use this due to high CPU usage.

:pool_size vs worker_connections

In your Rainbows! config block, you may specify a Thread pool size to limit your application concurrency independently of worker_connections.

Rainbows! do
  use :CoolioThreadPool, :pool_size => 50
  worker_connections 100
end

In extremely rare cases, this may be combined with Rainbows::AppPool if you have different concurrency capabilities for different parts of your Rack application.

RubyGem Requirements

Originally generated with the Darkfish Rdoc Generator 2, modified by wrongdoc.

We love to hear from you!
Email patches (with git send-email), pull requests, questions, bug reports, suggestions, etc. to us publically at rainbows-talk@rubyforge.org.
No subscription to the mailing list is necessary, just let us know to Cc: you if you're unsubscribed.
To subscribe, email rainbows-talk-request@rubyforge.org with "subscribe" in the Subject and respond to the automated confirmation message.
Do not waste bandwidth with HTML, HTML mail will not be read.
Quote only parts you're responding to and do not top post.
For sensitive topics, email us privately at rainbows@bogomips.org.