On 2/14/06, Alan Kennedy <[EMAIL PROTECTED]> wrote: > [Ian Bicking] > > Note that the scope of a WSGI server is very very limited. It is quite > > distinct from an XMLRPC server from that perspective -- an XMLRPC server > > actually *does* something. A WSGI server does nothing but delegate. > > and > > > I'm not set on "production" quality code, but I think the general > > sentiment against that is entirely premature. The implementations > > brought up -- CherryPy's > > (http://svn.cherrypy.org/trunk/cherrypy/_cphttpserver.py) and Paste's > > (http://svn.pythonpaste.org/Paste/trunk/paste/httpserver.py) and > > wsgiref's > > (http://cvs.eby-sarna.com/wsgiref/src/wsgiref/simple_server.py?rev=1.2&view=markup) > > are all pretty short. It would be better to discuss the particulars. Is > > there a code path in one or more of these servers which you think is > > unneeded and problematic? > > A few points. > > 1. My opinion is not relevant to whether/which WSGI server goes into the > standard library. What's required is for someone to propose to > python-dev that a particular WSGI server should go into the standard > library. I imagine that the response on python-dev to the proposer is > going to be along the lines of "Will you be maintaining this?" If/when > python-dev is happy, then it'll go into the distribution. > > 2. What's wrong with leaving the current situation as-is, i.e. the > available WSGI implementations are listed on the WSGI Moin page > > http://wiki.python.org/moin/WSGIImplementations > > 3. If I had to pick one of the 3 you suggested, I'd pick the last one, > i.e. PJE's, because it fulfills exactly the criteria I listed > > - It's pretty much the simplest possible implementation, meaning it's > easiest to understand. > - It's based on the existing *HttpServer hierarchy > - It's got a big notice at the top saying """This is both an example > of how WSGI can be implemented, and a basis for running simple web > applications on a local machine, such as might be done when testing or > debugging an application. It has not been reviewed for security issues, > however, and we strongly recommend that you use a "real" web server for > production use."""
Let's make it so. I propose to add wsgiref to the standard library and nothing more. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
