On Aug 29, 2008, at 9:03 AM, Petko wrote:
I do not understand why this happens, since all the information about the session is stored in the cookie itself and it should not use any in-memory data for reconstructing it. While browsing the sources of Beaker I noticed that it uses the PID to create the session ID, but I did not find any place where it actually uses it to verify the cookie that is received from the browser. Furthermore, when I switched mod_wsgi to daemon mode, the problem was solved and all requests are handled correctly. Still, I will need the embedded mode of mod_wsgi to achieve higher performance in the production.So, my question is: Is it possible and how to use Beaker cookie-only sessions together with the embedded mode of mod_wsgi on Apache?
Of course, I'm using cookie-based sessions with 8 paster process on 2 different machines in a cluster and don't see the invalidation that you're seeing. Could you try upgrading to the latest Beaker?
Cheers, Ben
smime.p7s
Description: S/MIME cryptographic signature
