Hi, I need some help from experienced web2py developers and creators. I am creating a new application and would like to know what a good architecture for a web2py application looks like. Here is the architecture diagram of the past web2py projects I have worked on.
<https://lh3.googleusercontent.com/-bcaLfPKsBTk/WC2TrYGXl8I/AAAAAAAAAAM/NvG5clFSHYg1gO7DfufouT1yTd38wJwRwCLcB/s1600/VMI%2BArchitecture%2BDiagram.png> Thin controllers and thick models is how I'm thinking of proceeding. The controllers talk to the database only via Business Objects (BO). Only BOs can access the database. There is a separate folder for the BOs inside the modules folder. app_name -> modules -> businessObjects -> DALs -> DalOfBO Each BO file contains a class for that BO and some methods. Should the methods have database queries in the same file or should there be a different file for the DAL operations, for each BO? Is this structure appropriate? If not, how can I make it better in order to make the development and maintenance of code easier. Thanks -- 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.
