Re: Mason + FastCGI

Pedro Melo <[email protected]> Thu, 1 Oct 2009 16:22:06 +0100
Newsgroups gmane.comp.web.mason.devel
Message-ID <[email protected]>
Hi,

On 2009/10/01, at 13:09, Hans Dieter Pearcey wrote:
> Excerpts from Pedro Melo's message of Thu Oct 01 02:55:28 -0400 2009:
>>> OK; then why not use only what you need?  It'd be trivial to write
>>> an app whose
>>> Controller::Root had a single action (at /, with any number of args)
>>> that
>>> handed off to a Mason view to do the real work.  You get fastcgi and
>>> the
>>> standalone server for free AND the Mason component reloading that
>>> you enjoy so
>>> much.
>>
>> That would work, but isn't that a bit extreme? Use the entire Cat
>> stack just to get FastCGI?
>
> * FastCGI
> * standalone dev server
> * futureproofing

Of these, FastCGI is true, standalone dev server is not important as I  
previously explained (I don't even use for Cat apps...) and future- 
proofing is a non-issue.


> I don't understand saying "the entire Cat stack".  It's not like I'm  
> pulling in
> a session module and an ORM and a form builder and a twitter client  
> -- it's
> just a HTTP abstraction and a URI dispatcher[1].  If we were talking  
> about
> Jifty I might get where you're coming from.

but I just need the HTTP abstraction.

PSGI is a much better fit, and probably my path is to help myiagawa to  
finish the HandlerPSGI + the Impl::FastCGI.

In the mean time, I'll try my HandlerFastCGI code to keep developing.

Best regards,

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf