[Twisted-web] asynchronous WSGI implementation
Steve Steiner (listsin)
listsin at integrateddevcorp.com
Fri Apr 9 06:59:28 EDT 2010
On Apr 9, 2010, at 6:32 AM, Manlio Perillo wrote:
> I have started to write an asynchronous WSGI implementation for
> Twisted Web.
> The code is available from a Mercurial repository:
> The WSGI application is executed in the main Twisted thread, and the
> application will be able to directly use Twisted features.
> The reason I'm doing this is because I have written a WSGI
> implementation for Nginx:
Maybe put on BitBucket? It'd sure be easier to patch/submit pull requests/file tickets on a public repo.
> and I would like to have a *similar* implementation written in pure
> Python, for testing purpose.
Will these share, or be able to use, the same demo/test code? I'd love to have the option to use Twisted from a WSGI app.
Have you resolved the issues you brought up and have been discussing with PJE over on web-sig? Which WSGI are you supporting?
This seems like a different thing than the greenlet/mako thing you were discussing over there.
> By the way: it seems that the WSGI implementation in Twisted Web has
> some bugs:
> * close method of the application iterator is not called in case of
> * _sendResponseHeaders does not check if start_response has been called
Before someone else says it... please file bugs (helpfully with test cases) at twistedmatrix.com/trac.
More information about the Twisted-web