> The current idea of Anthony is to directly use wsgihandler as the wrapper >
No, the "wrapper" would be a callable object, and it can be defined anywhere. wsgihandler.py is just the entry point -- you could import the wrapper in wsgihandler.py and then expose it to the web server (as in the built-in version of wsgihandler.py). However, a more important issue is that the installer needs access to the > HTTP server configuration at a deep level, if he wants to choose the > location of the wrapper. > No, the installer would need the same level of access to the server configuration as usual. The installer is going to have to set up some kind of handler for the web server no matter what. The only difference here is that handler would have to include a wrapper callable (possibly defined in an external module, which can be installed wherever desired). And of course, the wrapper must be defined somewhere, somehow, no matter what approach is taken. > This breaks one of the requirements in the use case: the installer might > not have access to the environment, except the minimal needed to install a > web application. > If the installer can install web2py at all, the installer can also set up WSGI middleware -- it can all be done with plain Python files contained solely within the /web2py folder. Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
