Thanks for the Auth / Acl suggestions. My choice of subject header may have been misleading. I am more interested in how people separate their code into a modules, particularly modules whose data and UI must be tightly integrated into the final project.
User id's and locale information for example will need to be accessed by application specific UI's and included in application specific schemas. Administration, reporting, archiving and other similar functions seem perfect candidates for being modules, but would like to see how others have done so successfully. - Steve W. dmitrybelyakov wrote: > > > > 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. >> > > Hi, > > I am at the moment reading an article/tutorial on how to implement and > Auth/Acl system with Zend. Sp here is the link: > http://codeutopia.net/blog/2009/02/06/zend_acl-part-1-misconceptions-and-simple-acls/ > > It has 3 parts of tutorial going from simple hardcoded acl with > users/usergroups/permissions > to building dynamic access control. Hope that helps. > > > > Dmitry. > -- View this message in context: http://www.nabble.com/User-Registration-and-Login-Management-Module---Best-Practice-Blueprint-or-Example-for-1.8-tp23952440p23972955.html Sent from the Zend Framework mailing list archive at Nabble.com.
