Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the accepted best practice with the Zend Framework’s new module system in version 2? Is it the intention that I create one module per controller for my application, or am I supposed to use the modules to group related controllers and their models together in some way?
See Rob Allens introduction into Modules or Matthews introduction into Modules.
In Short: A module is simply a bunch of Classes that perform one specific task. I.E.: A
Guestbookcould be one Module.GuestbookMailingcould be another module (but doesn’t need to be). You can have multiple Controllers, Models, Views in your Module. But it should be all tied to one part of your whole application.