Message94867
This is not an issue with CGI, but an issue with using an inappropriate
WSGI handler for a long-running process environment that only emulates CGI.
That is, in a true CGI environment, there can't be *multiple* requests
made to CGIHandler, and so it can't leak. In "normal" (i.e. pre-GAE)
long-running web environments, os.environ would not contain any request
information, only the process startup environment.
This limitation of CGIHandler should be better documented, but it's a
natural consequence of its design. The os_environ and base_environ
variables are provided so that subclasses with specialized needs can
handle them differently, and GAE is definitely a specialized need.
If someone wants to provide a GAEHandler class, great; otherwise, the
documented way to run a WSGI app under GAE is the
google.appengine.ext.webapp.util.run_wsgi_app function. |
|
Date |
User |
Action |
Args |
2009-11-03 19:05:20 | pje | set | recipients:
+ pje, snprbob86 |
2009-11-03 19:05:20 | pje | set | messageid: <1257275120.05.0.460450812771.issue7250@psf.upfronthosting.co.za> |
2009-11-03 19:05:17 | pje | link | issue7250 messages |
2009-11-03 19:05:17 | pje | create | |
|