32 messages in com.googlegroups.pylons-discussRe: Fast Python webserver
FromSent OnAttachments
Ian Bicking16 Feb 2007 15:15 
Robert Leftwich16 Feb 2007 15:49 
Ian Bicking16 Feb 2007 15:56 
Ben Bangert16 Feb 2007 16:01 
Robert Leftwich16 Feb 2007 17:19 
James Gardner18 Feb 2007 09:49 
Cliff Wells18 Feb 2007 11:36 
Bob Ippolito18 Feb 2007 12:19 
Cliff Wells18 Feb 2007 12:47 
James Gardner18 Feb 2007 13:21 
Ian Bicking18 Feb 2007 13:36 
James Gardner18 Feb 2007 14:00 
Bob Ippolito18 Feb 2007 14:20 
James Gardner18 Feb 2007 14:51 
Robert Leftwich18 Feb 2007 15:09 
James Gardner18 Feb 2007 15:41 
Robert Leftwich18 Feb 2007 15:59 
Cliff Wells18 Feb 2007 16:03 
Matt Good18 Feb 2007 23:26 
Robert Leftwich18 Feb 2007 23:54 
Max Ischenko19 Feb 2007 04:19 
Jose Galvez19 Feb 2007 09:56 
John_Nowlan19 Feb 2007 13:09 
wyatt-bC19 Feb 2007 19:00 
Shannon -jj Behrens20 Feb 2007 16:48 
Sean Davis20 Feb 2007 17:37 
Graham Dumpleton20 Feb 2007 19:54 
Sean Davis21 Feb 2007 04:41 
John_Nowlan21 Feb 2007 09:19 
Robert Leftwich21 Feb 2007 16:23 
Cliff Wells22 Feb 2007 14:46 
Robert Leftwich03 Mar 2007 22:03 
Subject:Re: Fast Python webserver
From:Max Ischenko (isch@public.gmane.org)
Date:02/19/2007 04:19:50 AM
List:com.googlegroups.pylons-discuss

On Feb 19, 12:21 am, "Bob Ippolito"
<b...-Zl9L/4BaIfTQT0dZR+Al@public.gmane.org> wrote:

I'm curious as to why anyone would want to use FastCGI in the first place if proxying is available? Implementation wise, there's very little reason why FastCGI would be markedly faster or slower than the HTTP protocol.

May be due to lack of appropriate knowledge?

For instance, official Pylons deployment docs talks about FastCGI plus Apache option only. Pylons wiki lists more deployment option but I am not sure whether it covers proxying setup either (I am not sure what is this really).

Max.