> > 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 could likely build some kind of helper that would achieve this, and LOAD(..., ajax=False) probably comes close (not sure it works across applications as is, and there may be some edge cases where it fails). However, I don't think anyone is going to put in the effort absent a compelling use case (which apparently hasn't come up in web2py's nine year existence). I also contend that Application A generally would not end up looking like a standard application but would instead just include some specialized pre-processing and post-processing code, so the superficial resemblance to a standard application (i.e., exists inside the /applications folder) would not be particularly meaningful. For that matter, nothing would stop you from putting some WSGI middleware inside an /applications folder if that superficial structure is important to you. I would also like to see an example from a PHP framework or elsewhere that is as simple as the above description. Anyway, if this particular approach is important to you, you might have better luck with Flask (see blueprints <http://flask.pocoo.org/docs/0.11/blueprints/>-- fair warning, a blueprint is not technically an application, so also fails your strict definition -- please direct all complaints to the Flask community), or perhaps a PHP framework. 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.
