Re: null pointer protection in DefaultTurbineRunData.setUser()...

[Brian Lawler]

The lazy loading-ness of my implementation is simply a 
re-implementation of getPermissions() and getRoles() that tries the map 
then goes to the database if not in the map.  I would just submit the 
class outright except that it references the tribe implementations of 
group, role, and permission.  I would need to spend some time to work 
it into the new TorqueSecurityService so that the configuration can set 
up which classes the ACL should be using...

-Brian

On Apr 3, 2004, at 6:06 AM, Scott Eade wrote:

Brian Lawler wrote:

Another issue we ran into was that creating ACLs became heavy, and  
caching the ACL in your session meant that if your permissions were  
changed by someone else - a site administrator or tribe moderator - 
you  would not see those changes until the next time you logged in.  
With  each membership to a tribe being represented as a role in a 
group the  reloading of all ACL information for each request also 
became  prohibitive.   The solution was to go with a lazy-loading ACL 
 implementation (which I will be glad to contribute - it's not a very 
 big deal)
It would be good to see a lazy-loading ACL implementation in the 
non-Hibernate models.

As Eric said, keep the patches coming.

Scott

--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
---------------------------------------------------------------------
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]