You could quite easily subclass the DBUserManager and cache the results once they came down.
Other options are: Get torque Managers to function, they will cache result sets for a while > -----Original Message----- > From: Gary Baker [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 30, 2003 8:43 PM > To: Turbine Users List > Subject: Security service and caching. > > > Anyone know how to configure the security service to cache > users, roles, > etc. > > I looked in > "org.apache.turbine.services.security.db.DBUserManager" and > it looks like it will hit the database everytime. Is there some other > security manager available? Maybe it's a configuration thing? > > -G > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
