[TYPO3-50-general] Last minute concept fix? Incosistent class naming for domain models ...

Martin Kutschker masi-no at spam-typo3.org
Mon Jun 1 22:11:22 CEST 2009

Daniel P?ötzinger schrieb:

> That might look good on the first place - but normally thats not how you
> want to group your Domain Model.
> If the application grows you rather want to group them in packages (with
> high coupling - low cohesion) like:
> Domain/Model/
>   Customer/
>   Products/
>   Contract/
>   Order/
>     Payment/
>   ...

Wouldn't that be like this?

   Customer.php (or CustomerModel.php)

When you group the files per "package" (or "module") than it makes IMHO
little sense to have "Model" in the directory name.


More information about the TYPO3-project-5_0-general mailing list