[TurboGears] Re: Identity Introspection

[Alberto Valverde]

PEAKs binding.metadata would have been of great help in this use-case. It let's you assign "permission metadata" to any method/attribute which you can then query through permissionFor. http://peak.telecommunity.com/doc/src/peak/security/  Alberto On 18/02/2006, at 2:18, Jeff Watkins wrote: Wow. That's a really interesting idea. I could easily expose the permission predicate that the require decorator is using, however, I don't think that would work, because later decorators would hide that information. Anyone with deeper Python-fu who'd like to make a suggestion? On 17 Feb, 2006, at 4:38 pm, Randall wrote: Close.  Since I've already defined the permission level in the controller, I don't want to define it again in the template. The links will be created based on how they are defined.  Links may be defined like so : [{'display': Efile, 'href':None, 'control':'Efile.index'}, {'display':'Google', href:'http://google.com', 'control':None}] The first item links to a controller method.  The second to an outside source.  When the first link is being created, Efile.index (controller method) will be inspected to see if the current user has permission to access it.  If not, the link will not be displayed. What I don't know how to do yet is inspect Efile.index permissions. Randall --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to turbogears@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---