Is the wrapper code inside the wrapped application here? On Thursday, 23 June 2016 00:14:36 UTC-4, Anthony wrote: > > The installer creates the /applications/myapp folder and puts a single > __wrapper.py file inside the /models folder. The content of this wrapper > file would be sufficient to handle pre-processing of the request as well as > post-processing of the response. The application developer would send the > application to the installer, and it would simply be unpacked on top of the > /myapp folder, leaving the __wrapper.py file in place (alternatively, the > __wrapper.py file cold be copied in after). > > What is the wrapper application and what is the wrapped application here? I know the language is confusing. The wrapper is not really an application because it is only a wrapper. The wrapped application might not really be an application either, because it might need the wrapper to become an application. Still, it is not so bad. The wrapper has an important feature of a web application, because it receives the request and responds to it, with the help of the wrapped application. The wrapped application as all the components of a web applications, from the perspective of the author, it is the application, which will be wrapped. Anyway, this is only terminology. The important is that you understand the question. I want to know what is the wrapper application and what is the wrapped application in this proposal, to determine if they are separated or not.
If the wrapper application is outside the wrapped application, then why do you say that it shows that it is "unimportant" to have this property? How a proposal that has the property can show that having the property is not needed? Even if does not have the property, i.e., the wrapper is inside the wrapped application, it will not show that the property is unimportant. A proposal that fails to answer the requirement does not show that the requirement is unimportant. Anyway, the issue of important Vs unimportant is very relative. I think it is important. I think that what we do now is important and that makes this concept important. -- 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.
