I agree with you about, Rhino.Security should do few and fast RPC as possible. In one of my scenario I have a webapp which can call *a lot* of IsAllowed() per request, so the performance are quite important.
I'll write a test to expose the issue and I'll try to do a comparison between my previous XmlIn implementation and this one with subqueries. Thanks. On 11 Ott, 00:14, "Ayende Rahien" <[EMAIL PROTECTED]> wrote: > Michele, > Applied, I would appreciate a test that shows the issue, though. > My worry is that part of the design concepts for Rhino Security is the heavy > usage of the second level cache. The problem with this approach is the > potentially expensive queries against the rhino security tables. > I might need to optimize that in a future date, and I would like to know > that I am not going to break this scenario. > > On Fri, Oct 10, 2008 at 6:33 PM, Michele Cantelli <[EMAIL PROTECTED]>wrote: > > > In this patch the PermissionsService use a sub-query to found which groups > > contains the user. > > I also add an internal factory to create the commons DetachedCriterias to > > avoid duplicated code. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
