Pre-process a REQUEST before Zope does anything else
Hello! I am, uh..., reluctant to dig thru more code that I allready have, so if some one has an easy answer for the following I'd be a gratefull :-) For my user_folder product project(*), I need to be able do some processing for each and every request that is sent to zope to determine some enviromental thingies, *before* the request is processed by the main zope mechanisms. I would like this to happen transparently (i need to check into a database and do some time-out calculations to determine whether the session is still valid). Is there such a hook in AccessControl or in any other place? How to the various sessionmanagers deal with this? Thanks, /dario (*) it's not a new one, it's a customisation of an existing, and code will be provided to the original author so he can decide if it should be or not included in the product. - -------------------------------------------------------------------- Dario Lopez-Kästen Systems Developer Chalmers Univ. of Technology dario@ita.chalmers.se ICQ will yield no hits IT Systems & Services
[Dario Lopez-Kästen] | I need to be able do some processing for each and every request that | is sent to zope to determine some enviromental thingies, *before* | the request is processed by the main zope mechanisms. I'm not entirely sure, but you might be looking for something like this: <URL:http://www.zope.org/Members/michel/Projects/Interfaces/BeforePublishingTraverse> <URL:http://www.mit.edu/afs/sipb/project/python/doc/DevGuide/ObjectPublishing.html> __before_publishing_traverse__ (Yeah, I make an effort to find the worst URLs... ;-)
participants (2)
-
Dario Lopez-Kästen -
Erik Enge