> This discussion is challenging and it shows that you are right that use > cases are useful, if only to help frame a discussion. I think that your use > case is not to pass the configuration information, but the need for a > wrapper (for pre-processing and post-processing) >
No, that is *your* use case/requirement. You began this whole discussion with the idea of passing configuration information but claimed what you really cared about was a "wrapper application." I provided several very simple solutions for passing configuration information that did not entail "wrapping" the application, but you balked at those options, claiming what you really wanted was a way to "wrap" applications. So, I have obliged and attempted to identify possible solutions for you. Now you seem to be backtracking and claiming you really only care about passing configuration information, which is a very specific use case. That's fine, but don't make it sound like I'm trying to push the idea of a wrapper -- that has always been your requirement. Please go back and re-read your own writing. > Moreover, we do not even agree on what are valid use cases. You insist > that use cases should be real world use cases, > perhaps even consider that a use case has to come from the real world by > definition. I have the different view point that real world use cases are > important, but not enough and that abstract use cases are necessary if we > want to do development, I even think that the more we have a large scope, > such as creating a new approach to web programming, even more general than > a new language, the more we need abstract use cases. > You make it sound as if I have made general proclamations about the nature of innovation. We have not been having a discussion about abstract concepts related to new programming paradigms -- we have been discussing a very specific and concrete issue, namely the means by which you might do some pre/post-processing of requests in web2py. My mention of "use cases" and "requirements" is limited to that context. My point is that web2py seems to be able to satisfy the *use cases* you articulate (and probably many other related use cases) but not necessarily some seemingly unnecessary *requirements*. I simply argue that it is not worth putting in significant effort to meet those seemingly unnecessary requirements unless you can make a compelling case that those requirements are necessary and that the effort to meet them would be worth the benefit. You have not done so, nor even attempted to do so. You seem to think that merely by declaring a concept "abstract," it is necessarily important and therefore worth pursuing. Furthermore, as already noted, "real world" does not mean "currently existing." > In the last post, I did not try to evaluate your __wrapper.py example. in > terms of your use case or goal, which was to provide a wrapper for > pre-processing and post-processing. I tried to make a point in terms of the > use case that I stated originally, which was a need to pass the config > information under severe constraints. I never claimed that I had a > different way to do a wrapper application that fulfill your goal. > Here is a quote from you (in response to the __wrapper.py idea): *However, if your objective is to be able to pass the configuration information and the installer can use the application folder, I don't see why they would not use it to achieve this objective, no need for a wrapper.* In other words, you were claiming that the installer could somehow "use the application folder" to pass configuration information in a manner that was different from the __wrapper.py idea. I challenged you to write some code demonstrating that, but the code you wrote did not in fact "use the application folder," and therefore failed the challenge. Perhaps you now agree that your statement above is incorrect. Also, note that I never said the __wrapper.py method was a good solution for merely passing configuration information (as I already offered much simpler solutions, all of which you dismissed because they did not involve wrapping the application). Its purpose was to satisfy your more general request for application wrapping. 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.
