Bite-size ZF: Module-specific models

Jul 19, 2008 8:17:07 AM

If you're like me, you like to use different classes to represent the same model in different modules. The rationale is quite simple: by using different classes you're encapsulating module-specific business logic within that module. For instance, a user model in an admin module may require functions related to access control, whereas the model's counterpart in a website module might need functionality to send messages to other users.