Perhaps, you already provided the answer: wsgihandler.py is *where* you would call the entry point to your wrapper application (and by the way, it doesn't have to be there -- you could put it anywhere, as long as you tell your web server where it is), but the wrapper application code itself can be wherever you want, and it can be as complex as you want. It would indeed be separated from the wrapped application.
This seems to work. It is kind of a python application that wraps the framework. It is not a solution at the application level, but at the framework level, but it is fine, perhaps even better. I had to edit the path in wsgihandler.py because I moved it outside web2py, but this is fine. I don't mind to edit it, because it is not going to be erased or rewritten during an update. I feel guilty regarding the initial requirement that the wrapper application is a web2py application, which, made no sense given its purpose. -- 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.
