On 1/24/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > Anyway, these are not necessarily benefits for TurboGears' audience; > I'm just pointing out for the sake of anybody following this thread > what the intended benefits of peak.security are, so they can tell for > themselves whether eval() is indeed better for *their* use cases. :)
I do understand the use cases for peak.security, and I'm sure that some portion of TurboGears users will benefit from that. For the simple, yet common, cases that identity's current API solves nicely, I was thinking that eval() was just as good (plus low overhead) as creating a context that keys on class/method. You have a good point, though, that someone could create rules externally that override the individual method controls if it's all going into one big context. Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
