AW: [Zope3-Users] efficiency of PAU authentication
nxnth at yahoo.com.cn
Tue Apr 29 23:51:19 EDT 2008
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
# This is also a handy place to try and authenticate.
def afterTraversal(self, request, ob):
----- Original Message ----
From: Roger Ineichen <dev at projekt01.ch>
To: nixon <nxnth at yahoo.com.cn>; zope3-users at zope.org
Sent: Wednesday, April 30, 2008 11:26:31 AM
Subject: AW: [Zope3-Users] efficiency of PAU authentication
> Betreff: [Zope3-Users] efficiency of PAU authentication
> Hi, dear all,
> PAU authenticates 2 times each request, before and after traversal.
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
Yes, of corse, I recommend caching if you need to run a heavy loaded site.
> Best Regards
> ÑÅ»¢ÓÊÏä£¬ÄúµÄÖÕÉúÓÊÏä£¡ <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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Zope3-users