[mod_python] framework agnostics (was: Thread safety)

>From what I've understood, WSGI is just a way for framework developers
to be server-agnostic. If you develop an application framework, then
using WSGI as the interface with the web server allows you to be
independent of the web server, hence to run on Apache through
mod_python, on IIS through the WSGI wrapper (see
http://www.amorhq.net/blogs/index.php/fumanchu?blog=2&cat=15&page=1&disp=posts&paged=1),
on the BasicHTTPServer, on Twisted, etc.

Currently the problem is that choosing an application framework
usually involves choosing a web server. If I've understood it
correctly, WSGI is there to provide a server-agnostic platform for
application framework developers to build on top, so its targets
audience is not the final application developer. So the end result for
the application developer is that he can pick the web server he wants,
pick the application framework he wants, and start coding.

WSGI is too low level to develop big applications. Like CGI or
Servlets, it's a very low level API, and unless you like to reinvent
the wheel and implement an application framework yourself, you need an
application framework to efficiently build some applications.

Building a WSGI interface on top of mod_python would therefore make
mod_python more friendly to application framework developers ; they
would not have to fight and build a wrapping layer around the
mod_python API (which mainly revolves around the request object).

Regards,
Nicolas

2005/6/8, Graham Dumpleton <grahamd at dscpl.com.au>:
> 
> On 08/06/2005, at 1:54 PM, Graham Dumpleton wrote:
> >
> > phase, the ability to work with other Python modules such as mod_ssl
> > etc etc.
> 
> Whoops, read as "other Apache modules such as mod_ssl".
> 
> _______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://mailman.modpython.org/mailman/listinfo/mod_python
>