From: NewtonApple <newtonapple@...>
Date: 2008-01-23T13:44:58+09:00
Subject: Re: Announcing Revactor: an Actor model implementation for Ruby 1.9

> Using Reactor means you must abandon any code which is structured around
> making synchronous blocking calls to interact with the network.  This
> includes pretty much everything built on the traditional imperative sockets
> API.  Everything must use an asynchronous API.  There are ways around this,
> such as spinning off any synchronous blocking calls in a separate thread,
> but then you need a thread for each blocking call you wish to make, and
> there are performance issues with threads and I/O in Ruby, not to mention
> the traditional pitfalls of threaded programming.


How does Revactor do in terms of memory?  I know for things like
Stackless Python and Erlang, they can spawn thousands of threads
without even blinking...  How does Revactor fare in this regard?