Massimo, Thank you for the guidance on structuring the application, that helps a lot. However, it seems to me that there is no scope for creating a deeper hierarchy than Application/Controller/Action, is this correct? Would this be an inherent part of any web framework which does the URL mapping for you? Do people find this to be a limitation?
I tried experimenting within an application called "TestComplaint", web2py allows me to create the files: "Complaint/ClientComplaint.py" and "Complaint/ClientComplaint/index.html" which creates sub-folders in the controller and view folders. Trying to enter the corresponding URLs obviously fails as it is looking for a method "ClientComplaint" in the controller "Complaint", so these files would never be accessible... I'm not saying web2py should stop me from creating them, but just curious if there was a good reason for allowing me to do so, with a view to creating sub- application folders? regards, Andy. On Apr 8, 1:58 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > Hi Andy, > > One important issue here is whether all the applications you are going > to build with web2py need to share authentication with non-web2py > applications or not. If yes you need federated authentication (for > example CAS) and things can get complex. If no, then you can simply > your life a lot if > > 1) make a single controller for each complaint > 2) make a single model for all complains > 3) extend your application with one controller and one model file for > each main function of the company > > This design will allow to easily share the built-in authentication > (auth and db.py) and layout.html > It is modular enough that if you later choose to break it into > separate apps and implement some other distriuted authentication > mechanism you can do so. > > Massimo > > On Apr 8, 3:42 am, AndyBuchan <mr_buc...@hotmail.com> wrote: > > -- To unsubscribe, reply using "remove me" as the subject.
