there are classes for Authentication and ACL that u can use. i have tried using them but now they seem alittle wierd to use. as in the Zend_Auth provides the Identity which i think is the user id or name i cant rmb but they shld include a usergroup field for use with Zend_Acl. plus i must always query Zend_Acl to determine if the user is allowed access to the resource ... i am thinking it shld integrate better with Zend_Layouts and Zend_Navigation. Zend_Layouts as in sometimes i want to display things that maybe a specific usergrp can view but not others etc
that said i think there shld still be standards for this. i think it will make it more maintainable by a team rather than diff ppl implementing it differently . swilhelm wrote: > > I would like see best practice blueprint or example for implementing > modules in 1.8. > > A user registration and login management module would be ideal. > > Any suggestions? Thanks in advance. > > - Steve W. > -- View this message in context: http://www.nabble.com/User-Registration-and-Login-Management-Module---Best-Practice-Blueprint-or-Example-for-1.8-tp23952440p23954832.html Sent from the Zend Framework mailing list archive at Nabble.com.
