[wsgi] Python interpreter initialization

[Cliff Wells]

On Tue, 2007-08-21 at 09:17 +0200, Manlio Perillo wrote:
> Cliff Wells ha scritto:
> > On Mon, 2007-08-20 at 12:51 +0200, Manlio Perillo wrote:
> > 
> >> This is not a really big problem, since the *right way* to deploy 
> >> mod_wsgi is to use another nginx proxy server behind the nginx server 
> >> with mod_wsgi; so I can just restart the server (and the proxy can limit 
> >> the number of request to the wsgi nginx server).
> > 
> > This makes me wonder if writing a mod_ajp wouldn't be more efficient in
> > the long run.  ajp-wsgi is already out there and runs as a separate
> > server, so these would be non-issues.
> > 
> > http://www.saddi.com/software/news/archives/49-ajp-wsgi.html
> > 
> 
> Why should we implement and use server that speaks languages other then 
> HTTP?

1.  Because it would allow you to get WSGI support without embedding a
Python interpreter in Nginx.

2.  Because it would allow you to utilize an existing piece of software
(ajp-wsgi).

3.  Because the same work would benefit both the Java/Tomcat crowd as
well as the Python crowd.

Overall, it seems like *much* less work and I'd be surprised if there
were much of a performance difference at the end of the day.

Regards,
Cliff