> > @anthony > why db, auth and mail must define current in models while request, > response, session, cache, and T objects, can work on the fly in modules > without define current (e.g. current.T) in models? >
request, response, session, cache, and T are all web2py API objects, so they can be added to current automatically by the framework (before hitting your app code). Things like db, auth, and mail are all created in your app code, so (a) the framework cannot assume they will exist (or will exist with those particular names, which are not mandatory and simply used by convention), and (b) the framework could not add them because they are not created until your app code is executed. 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
