Hi,
in app.publication.zopepublication.py there are 2 methods.
Maybe they are invoked in different scenarios, I am not sure.
But at least one PAU auth for each request.
def callTraversalHooks(self, request, ob):
# Call __before_publishing_traverse__ hooks
notify(BeforeTraverseEvent(ob, request))
# This is also a handy place to try and authenticate.
self._maybePlacefullyAuthenticate(request, ob)
def afterTraversal(self, request, ob):
#recordMetaData(object, request)
self._maybePlacefullyAuthenticate(request, ob)
----- Original Message ----
From: Roger Ineichen <[EMAIL PROTECTED]>
To: nixon <[EMAIL PROTECTED]>; zope3-users@zope.org
Sent: Wednesday, April 30, 2008 11:26:31 AM
Subject: AW: [Zope3-Users] efficiency of PAU authentication
Hi Nixon
> Betreff: [Zope3-Users] efficiency of PAU authentication
>
> Hi, dear all,
>
> PAU authenticates 2 times each request, before and after traversal.
Really?
Can you explain why this happens?
> What if I make an authentication plugin based on relational database?
> Everytime the plugin has to create a pricipal from database,
> assign roles to it, ...
> When the website is under heavy load, there must be huge
> number of authentication request.
> Is RDB based PAU efficient enough to do authentication?
>
> I have an idea of session-cache authentication: fetch
> credentials from RDB and cache them in session. Is this more
> efficient?
Yes, of corse, I recommend caching if you need to run a heavy loaded site.
Regards
Roger Ineichen
> Best Regards
> Nixon
>
>
> ________________________________
>
> 雅虎邮箱，您的终生邮箱！ <http://cn.mail.yahoo.com/>
>
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ_______________________________________________
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users
