Hi, I am implementing an application that is structured in way where I have a business model and multiple Pyramid applications on top of that, ending up with 4 processes, two of them providing APIs (XML-RPC) and two of them providing UIs.
I'm happy using the ACLAuthenticationPolicy but I noticed that my __acl__ methods are getting convoluted as they have to know about the various processes. I wanted to split this up and wondered why the ACLAuthorizationPolicy can't be customized to use different attributes for the lookup. I'm making separate instances of the ACLAuthorizationPolicy in those applications and thus I started out to customize it, but had to copy the whole class. The ACL system itself seems fine for me, but putting the variations of ACLs that I'm dealing with into the same __acl__ is ... well ... convoluted. Chris pointed out that "adding knobs" isn't that fashionable - but I AFAICT I'm happy with the ACLAuthorizationPolicy "except this one bit". I know this isn't necessarily a strong argument but maybe somone can tell me whether I'm doing something wrong or maybe help me to work towards a "no knobs needed" solution. :) Cheers, Theuni -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
