granma said : 'everything is wonderful if you know how to appreciate it' imho
models : yet in the books said that is better to not put the logic function in models - Minimize the code in models: do not define functions there, define functions in the controllers that need them or - even better - define functions in modules, import them and use those functions as needed. i think it because the models is execute everytime the apps running, but if you define response.models_to_run you can minimalize the unnecessary function to load or execute that you define in models everytime the apps is running. controllers : this is the place where programmers usually put the logic function. modules : i think this is same like controllers with some of benefits. 1. you can call it the logic function define in modules in other application. 2. the web2py modules is like python modules, it automatically compile it, so you will got *pyc for every module you create in here, and i think it will increaase the performance in byte compile rather in script. just a suggestion if you want to create function that can't be execute or retrieve via browser (people can't see the return value) i think, it's better to put the __ in the function name. e.g. def __check_purchase_status(): please correct and forgive me if i'm wrong. best regards, stifan -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
