I'm trying to wrap my brain around some of these concepts as well. Just out of curiosity, who all uses module specific models?
In the case of dasprids.de (source: http://site.svn.dasprids.de/) Ben separates the models into their respective module utilizing the "default" module somewhat as a common/system module (ie. users, etc). That approach works fine for a simple/straightforward system, but I could see how it could get a little confusing and unmaintainable if the data structures and modules were either more complex or there were several modules that had overlapping "ownership" of different models. I have a feeling that this will naturally end with a "use what works for your application" type of argument, but even knowing that not everyone will have the same requirements/expectations/style, I still can't help but search for a unified "best practice". Thoughts? -- View this message in context: http://n4.nabble.com/Doctrine-default-directory-structure-tp947943p1678148.html Sent from the Zend Framework mailing list archive at Nabble.com.
