Is it possible configure mod_wsgi to recognize WSGI application script
files without explicitly declaring the application object within each
script file? If not, is there a elegant/crude work-around?
Along the same lines, if that were possible, it would be nice to also
assume defaults for the return variables of the start_response
function so it (start_response) wouldn't have to be declared
explicitly. Then, any changes to the defaults or to the environ
settings could optionally be set/declared and retrieved in the script
file:
<%
# default status = '200 OK'
start_response('403 Forbidden', [('Content-Type', 'text/html')])
var = "Access Denied"
%>
<html>
<body>
{var}
</body>
</html>
The above example also assumes there would be no need to explicitly
return content because the processed script file itself would serve as
the return content. Admittedly, the goal is a bit unconventional
having the template file serve also as the wsgi application script
file with several assumptions built-in. The motivation if it's not
already obvious is to return to a one file per URL application
environment along the lines of PHP (performance and security issues
permitting).
-Walter
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---
