well, i implemented a simple authn/authz system that works with TG. like the allow_only attribute of a controller and the require decorator but i'm glad there will be a fix.
On Aug 9, 4:44 am, Michael Pedersen <[email protected]> wrote: > This is one of the weaknesses. The system needs a way to identify the user > for a given session. This means loading up the user object as well. Now, we > should be able to have a better way to handle it, and caching should be > enabled, but there is at least a reason. > > Fortunately, somebody has opened a ticket for it, and we'll get a fix for > this in soon. > > > > > > > > > > On Mon, Aug 1, 2011 at 7:15 AM, Mengu <[email protected]> wrote: > > Hi all, > > > I don't know if it's repoze.who or TurboGears doing that but in every > > request it sends 3 db requests to user, group and the permission > > tables. Why is this necessary? I don't want this to happen. This > > information can stay in session until it expires. Please lighten my > > way here. > > > -- > > You received this message because you are subscribed to the Google Groups > > "TurboGears" 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/turbogears?hl=en. > > -- > Michael J. Pedersen > My IM IDs: Jabber/[email protected], AIM/pedermj022171 > Yahoo/pedermj2002, MSN/[email protected] > My LinkedIn Profile:http://www.linkedin.com/in/michaeljpedersen > Twitter: pedersentg -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
