On Tuesday, 21 June 2016 01:27:05 UTC-4, Anthony wrote: > > You make claims about how a "wrapper application" *must* look without >>> demonstrating *why* it must look like that. >>> >> >> Yes and they are not based on any use case. They are based on what seems >> natural. Some times, we have definitions that are just there because they >> are natural and we can more easily say things about them, by keeping them >> simple and natural. >> > > If you want (1) Application A to be a standard web2py application in the > /applications folder, with models, controllers, etc. that receives HTTP > requests and handles them by executing the application code in the standard > manner, and (2) Application B, also a standard web2py application in the > /applications folder, and (3) a single line in Application A that simply > "includes" Application B, thereby magically routing all requests to > Application B (after some initial processing, and possibly with some > additional manipulation of the response after Application B returns), then > there is no simple built-in way to achieve that. >
You have a point. I required that the wrapper application is a standard web2py application, but this is not reasonable and achieves no purpose. I feel so ashamed that I did not realize that this was perhaps the issue that bothered you. This requirement is in contradiction with the fact that the only purpose of the wrapper is to include the wrapped application, after a little preparation. Using a complete framework for the wrapper, insisting that it loads its library, defines constants, including paths to itself, define the database connexion, etc. when the purpose is to include the entire framework again is indeed weird and it's going to fail because constants are already defined and they cannot be redefined. When I said that it was easy in PHP, it's because I see PHP itself as the framework for WEB applications, in the following sense that it is built to generate web pages. In an unfair way, I did not had the requirement that the wrapper for an application created in some specialized framework has to be an application in the same framework. So, of course, it can be any separate web application in the language, python in the case of web2py, PHP in the case of a PHP framework, in fact the most simple application possible in that language. To my defense, I can say that, given that you have been proposing alternative solutions, you could have suggested from the start that we relax the condition that the wrapped application is a web2py application. -- 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.
