How would you structure Zend_Auth & Zend_Acl in Zend Framework to obey having a Thin Controller?

Best solution is Front Controller Plugin. In routeShutdown() method (i.e. First moment when you have the request object) you check the ACL and / or redirect to login controller.

And if you need calling restricted action in non-restricted controllers you should move the code to predispatch. – TomáÅ¡ Fejfar Jun 7 '09 at 9:57 Interesting. I'll need to research routeShutdown().

– joedevon Jun 8 '09 at 15:40 I'm having a tough time figuring out how and where to register the front controller plugin. Do I have to modify the new Bootstrap. Php?

– joedevon Jun 9 '09 at 9:15 Yes, you do. Use $front->registerPlugin($pluginInstance); – TomáÅ¡ Fejfar Jun 13 '09 at 19:31 1 I don't totaly agree with this response, it is a valid answer however, but it only applies to simple use case, most people see "resource" == "controller" (or action) but you may have more complex acl where your resource can be anything, and in that case you can't rely on a front controller plugin because you're not able to provide anything else than a request object to the Acl module. I'll go for an AuthorizationService which extends Zend_Acl, it's a little more work, especially when you need to redirect user to an error/login page but it's worth to do it.

– JohnT May 16 at 20:24.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.