From: "aemadrid@..." <aemadrid@...>
Date: 2008-01-23T08:39:59+09:00
Subject: Re: Announcing Revactor: an Actor model implementation for Ruby 1.9

I'm still trying to wrap my head around this whole concept. What is
the difference in approach between Revactor and EventMachine [1]? I
can see that one works with 1.8 and the other starts with 1.9 but they
seem to me, the uneducated reader, very similar. Am I missing
something?

Thanks in advance,


Adrian Madrid


On Jan 21, 12:13 am, Tony Arcieri <t...@clickcaster.com> wrote:
> [Note:  parts of this message were removed to make it a legal post.]
>
> I'm pleased to announce the initial public availability of Revactor, an
> Actor framework for Ruby 1.9. The Actor model has seen increasing popularity
> in languages like Erlang and Scala. Revactor adds asynchronous message
> passing to the Fibers mechanism, easing the development of concurrent
> programs using them. You can read more about the Actor model here:
>
> http://revactor.org/philosophy/
>
> Revactor also includes a high performance sockets API, largely compatible
> with Ruby's own, but which also seamlessly interoperate with the Actor API.
> Using this approach means you can simultaneously process messages from both
> sockets and other Actors. Furthermore, with a small amount of monkeypatching
> it's able to run Mongrel, using Actors instead of threads as the underlying
> concurrency mechanism. Initial tests of the performance of Mongrel on top of
> Revactor surpass the threaded version.
>
> Revactor is available as a gem and can be installed with:
>
> *gem install revactor*
>
> For additional information please see the web site:
>
> http://revactor.org
> --
> Tony Arcieri
> ClickCaster, Inc.
> t...@clickcaster.com