From: khaines@...
Date: 2007-05-13T06:10:22+09:00
Subject: Re: ANN: Swiftiply 0.5.0

On Sun, 13 May 2007, Rick DeNatale wrote:

> Okay, I missed that, so swiftipy_mongrel_rails is really a substitute
> for mongrel_cluster.

Maybe?  It was contributed by Ezra Z. and really just represents a 
starting place for figuring out the best way to support Rails users.

> I guess that you can also put this behind say Apache by setting the
> cluster_port to something other than 80 and using mod_proxy.

Yep.  In the documentation I used port 80 because one of the ways that I 
am using this with IOWA is without any other web server in front of it.

> I guess that one concern is tracking changes to the base mongrel.

(*nod*) The changes are all intended to be transparent to a mongrel 
handler, so the handlers don't know nor care whether they are running in a 
threaded mongrel, in an evented mongrel, or in a swiftiplied mongrel.

It just dawned on me that I did not do this in the gem I released last 
night, but I inteded to insert Mongrel 1.0.1 as a dependency, and will 
then keep the codebase current to the latest stable Mongrel release as 
time moves forward.

> Another would be how this interacts with deployment tools like
> Capistrano and Deprec.

I wouldn't think there is anything special needed for interaction with a 
deployment tool.  Can you expand on your concern there?


Thanks

Kirk Haines