On Mon, Feb 10, 2014 at 7:05 AM, jmleroux <[email protected]> wrote:
> Hello, > I don't know if this is relevant to keep only one module, but it is clearly > overkill to make a module per table. > The answer is probably somewhere in the middle. ;) > > > > -- > View this message in context: > http://zend-framework-community.634137.n4.nabble.com/Module-best-practice-tp4661655p4661656.html > Sent from the Zend Framework mailing list archive at Nabble.com. > > -- > List: [email protected] > Info: http://framework.zend.com/archives > Unsubscribe: [email protected] > > > A module is not the same thing as a model, keep that in mind. A module would be a particular section of your web site. For instance, if your site required users to login before they were able to do anything that could be considered a module. In essence a module is anything that can be pulled out of your application and used easily within another. I might suggest watching Evan's talk on Introduction to Modules to get a better understanding as to what they are, http://blog.evan.pro/introduction-to-modules-in-zend-framework-2-talk-at-zendcon-2012
