The thing I have found is the most helpful is to download the turbine source and poke around in the class itself (org.apache.turbine.util.security.AccessControlList). Not only will you get an understanding of the internal workings of Turbine, you will also get some good ideas on how to design your own application (IMOHO the Turbine developers are true experts when it comes to OO design).
Example, after poking around some of Turbine's Service code, I have decide to pipe all my data access through services (the same way BaseSecurityService/DBSecurityService and TurbineSecurity do ). This allows me to abstract access to the peer classes, so if I have to connect my app to a database with a different layout or something other than a database, the impact on my application as a whole is very minimal. Scott -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 13, 2000 7:55 AM To: [EMAIL PROTECTED] Subject: Turbine - AccessControlList Hello Can any one tell me the class "AccessControlList" (it is used for user's roles and permission ) Does it loades all the data in 'cash/memory' of a user and reades from memory or does it reades the Data base again and agin to see if the user has this permission or not. I need to know this for performance reasons. regards. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
