How would you structure Zend_Auth & Zend_Acl in the Zend Framework to subordinate to the Thin controller?

Question

There has been quite a lot of talk / discussion about thin controllers in the Zend Framework community lately. Obviously, ZF users tend to view the model as nothing more than a gateway to the database.

The argument is that models should be bold and do most of the work, and controllers should not bind methods and do a lot of work without passing the value to the user interface of the model.

For some links, follow the links in this post:

http://weierophinney.net/matthew/archives/200-Using-Zend_Form-in-Your-Models.html

At the same time, I think it's easy to let Zend_Acl and Zend_Auth overtake your controllers and turn them into a complicated mess.

I am creating a site right now when an administrator section is required and before writing this code, I thought that I would try to start a good discussion / debate about how to better structure authorization and access control with a special eye on well-tested methodologies from the OOP world.

Thanks.

Answer 1

The best solution is the Front Controller plugin. In the routeShutdown () method (i.e. the first time you have a request object) you check the ACL and / or redirect the login controller.