Redirecting to http://rainbows.bogomips.org/Rainbows/Revactor.html ...
Enables use of the Actor model through Revactor under Ruby 1.9.
Revactor dormant upstream, so the use of this is NOT recommended for new applications.
It spawns one long-lived Actor for every listen socket in the process and spawns a new Actor for every client connection accept()-ed. worker_connections will limit the number of client Actors we have running at any one time.
Applications using this model are required to be reentrant, but do not have to worry about race conditions unless they use threads internally. Rainbows! does not spawn threads under this model. Multiple instances of the same app may run in the same address space sequentially (but at interleaved points). Any network dependencies in the application using this model should be implemented using the Revactor library as well, to take advantage of the networking concurrency features this model provides.
revactor 0.1.5 or later