[Web-SIG] A 'shutdown' function in WSGI
Chris McDonough
chrism at plope.com
Tue Feb 21 03:21:55 CET 2012
On Mon, 2012-02-20 at 20:54 -0500, PJ Eby wrote:
> 2012/2/20 Chris McDonough <chrism at plope.com>
> On Mon, 2012-02-20 at 17:39 -0500, PJ Eby wrote:
> > The standard way to do this would be to define an "optional
> server
> > extension" API supplied in the environ; for example, a
> > 'x-wsgiorg.register_shutdown' function.
>
>
> Unlikely, AFACIT, as shutdown may happen when no request is
> active.
> Even if this somehow happened to not be the case, asking the
> application
> to put it in the environ is not useful, as the environ can't
> really be
> relied on to retain values "up" the call stack.
>
>
> "Optional server extension APIs" are things that the server puts in
> the environ, not things the app puts there. That's why it's
> 'register_shutdown', e.g.
> environ['x-wsgiorg.register_shutdown'](shutdown_function).
I get it now, but it's still not the right thing I don't think. Servers
shut down without issuing any requests at all.
- C
More information about the Web-SIG
mailing list