Redirecting to ...

Included Modules


Implements a basic single-threaded event model with EventMachine. It is capable of handling thousands of simultaneous client connections, but with only a single-threaded app dispatch. It is suited for slow clients, and can work with slow applications via asynchronous libraries such as async_sinatra, Cramp, and rack-fiber_pool.

It does not require your Rack application to be thread-safe, reentrancy is only required for the DevFdResponse body generator.

Compatibility: Whatever EventMachine ~> 0.12.10 and Unicorn both support, currently Ruby 1.8/1.9.

This model is compatible with users of “async.callback” in the Rack environment such as async_sinatra.

For a complete asynchronous framework, Cramp is fully supported when using this concurrency model.

This model is fully-compatible with rack-fiber_pool which allows each request to run inside its own Fiber after all request processing is complete.

Merb (and other frameworks/apps) supporting deferred? execution as documented at Rainbows::EventMachine::TryDefer

This model does not implement as streaming “rack.input” which allows the Rack application to process data as it arrives. This means “rack.input” will be fully buffered in memory or to a temporary file before the application is entered.

RubyGem Requirements

Public Instance Methods

em_client_class() view method source

Cramp (and possibly others) can subclass Rainbows::EventMachine::Client and provide the :em_client_class option. We /don't/ want to load Rainbows::EventMachine::Client in the master process since we need reloadability.

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
No subscription to the mailing list is necessary, just let us know to Cc: you if you're unsubscribed.
To subscribe, email 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