The cookbook. I keep missing that little gem every. Single. Time.
Thanks! ;) On 06/29/2012 06:30 PM, Michael Merickel wrote:
The cookbook illustrates a way to cache this information inside of `request.user`. The idea is that authenticated_userid and effective_principals both use request.user, and request.user uses unauthenticated_userid. While the cookbook shows how to do this via the callback mechanism, it is even more straightforward to do it in your own custom policy. http://docs.pylonsproject.org/projects/pyramid_cookbook/en/latest/auth/user_object.html#making-a-user-object-available-as-a-request-attribute
-- .oO V Oo. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
