Hi,

I didn't say it's better - it's EASIER. The reason it's easier is that
the mod_rails module is the one that actually manages the backend. That
means two major things:

1. You don't need to use mongrel_cluster or a FastCGI launcher
2. When the app die for some reason, the module will handle the
relaunching for you. This eliminate the need for something like monit or
a fastcgi spawner process.

There are also some other advantages like memory usage if you use Ruby
Enterprise Edition, but that's a different story. It does comes with a
global queue support (similar to what the EY balancer does).

Bye,

Guy.



Edho P Arief wrote:
> On Tue, Apr 28, 2009 at 10:36 PM, Guy Naor <guy@mor.ph> wrote:
>
>> Or if you are more adventurous try the new mod_rails for nginx. My tests
>> show it to be stable and fast, and though my production sites use mongrel,
>> it is sure easier to manage mod_rails.
>>
>> Guy.
>>
>>
>
> can you please enlighten me on this one?
> how exactly is this easier? I've read several information on this but
> still don't get why this method is better.
>
>
>