The goal is to have the security algorithm inside SecurityHelper and not inside each store, that way the security is consistent for all stores.
Maybe implement some caching of the permissions (it might already be cached inside slide). Dirk Sunny P wrote: > > Hello > > I was looking at implementing a Custom Store, the interface SecurityStore > has a method enumeratePermissions. I also looked at the SecurityHelper code. > It seems like the SecurityHelper asks the Store for all the Permissions > related to a particular URI. Then the SecurityHelper goes through each of > the Permissions to decide what kind of Permissions are available to a > specific User. > > On our system it is not very efficient to get all the Permissions associated > with a URI. Any specific reason why this was done in this way? Why not have > a method hasPermission which checks for the required Permission? > > Thanks -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
