Comment

Comment by bbbbbbbbb

> That said, a doc patch is always welcome - on github fork or via RT.

I would like to but I need to understand how this works to provide any patch whatsoever. What about porting a CGI::Fast application into the PSGI stack then?

while (my $req = CGI::Fast->new) { myApp->run($req); }

Is there a handler/wrapper for that?

I've read all the articles but it did not help much. WebGUI discovered FastCGI via a PSGI implementation but it's FastCGI who brought the speed, not PSGI per se. So it brings me back to my point...

> think Apache + FastCGI + CGI::Fast is the best thing in the world and you absolutely need nothing else

I think FastCGI was there to solve indeed a problem and did quite well at doing so. It could be Apache/Nginx/IIS + FastCGI&CGI::Fast, it would work too (Apache/IIS is from experience but Nginx is just an educated guess).

I've decided a long time ago that I will never go the mod_perl way (or at least, will not use their low level access API) then switched to FastCGI and been happy since then.

I still don't get it but perhaps one day it will hit me. I guess when somebody will bring a "Middleware" that will meet a need.

In the meantime, I will try to play with it on my spare time. I guess it will be the easiest way to discover what I might be missing...

If DotCloud does not offer this infrastructure(Nginx+FastCGI), it's ok, I still can use our actual providers and it will work (exactly the WebGUI article example for cheap providers!)

Thank you for your time!

parent bbbbbbbbb 15 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton