search

chadwhitacre / httpy

middleware to smooth over WSGI's most glaring warts.
0 stars 1 forks source link

learn to share #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The real goal here is to provide an HTTP server library that the Python
community can agree on. By which I mean, this is something the various web
frameworks could cooperate on. There's almost no chance for that to happen
if we don't offer robust WSGI support out of the box.

I think it would be appropriate to offer both Server and WSGIServer
classes. The latter could simply be a repackaging of what we find in
CherryPy (or elsewhere, although CherryPy's seems to be the only
production-ready one).

The real value of this is going to be when the guts are rewritten in C, a
la Mongrel. The takeaway now is: provide WSGI support OTB!

Original issue reported on code.google.com by whit537@gmail.com on 4 Nov 2006 at 1:49

GoogleCodeExporter commented 9 years ago 
Done. We're now using CP's server, so WSGI is baked in.

Original comment by whit537@gmail.com on 7 Nov 2006 at 5:16