On Sat, Apr 27, 2013 at 1:24 AM, Graham Dumpleton <graham.dumple...@gmail.com> wrote: > I described a different way of doing WSGI which would better cope with post > response hooks at the Python Web Summit at PyCon in 2012. It made use of the > context manager abstraction so it wouldn't screw with the returned iterable. > > http://www.slideshare.net/GrahamDumpleton/pycon-us-2012-state-of-wsgi-2-14808297
Also, wsgi_lite provides a way of registering resources to be closed post-response, that works within WSGI 1.0, also without altering the returned iterable: https://bitbucket.org/pje/wsgi_lite#close-and-resource-cleanups Although wsgi_lite provides programmatic support for this, it's internally implemented as a stock WSGI extension key ('wsgi_lite.closing') in the environ, and can be offered today by servers or middleware in a 1.0 environment. I just haven't gotten around to knocking out a PEP for it. _______________________________________________ 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
